For more information visit our Privacy Policy. Is any of my JSON data recorded or saved?Ībsolutely not! Your data is merely processed and returned directly to you. When in doubt, our recommendation is to validate JSON with the latest specification, RFC 8259, as it will ensure the highest level of compatibility. Which JSON specification should I choose? Yes! You can populate and process your JSON data automatically by submitting a GET or POST request ( example) with the following query parameters: dataįourspace, threespace, twospace, compact, or onetab preconditions and postconditions) in the configuration.Have questions? These are the answers to the questions we are most frequently asked. Checks Representation - A property of both the plan and state representations that describes the current status of any checks (e.g.Change Representation - A sub-object of plan output that describes changes to an object.Block Expressions Representation - A sub-object of a configuration representation that describes the expressions nested inside a block.Expression Representation - A sub-object of a configuration representation that describes an unevaluated expression.Configuration Representation - A sub-object of plan output that describes a parsed Terraform configuration.Values Representation - A sub-object of both plan and state output that describes current state or planned state.Plan Representation - The complete top-level object returned by terraform show -json.State Representation - The complete top-level object returned by terraform show -json.The JSON output format consists of the following objects and sub-objects: References wrapped in angle brackets (like ) are placeholders which, in the real output, would be replaced by an instance of the specified sub-object. To avoid excessive repetition, we've split the complete format into several discrete sub-objects, described under separate headers. Important elements are described with comments, which are prefixed with //. The following sections describe the JSON output format by example, using a pseudo-JSON notation. The Terraform 1.0 Compatibility Promises. We will introduce new major versions only within the bounds of Reject any input which reports an unsupported major "2.0", for changes that are notīackward-compatible. We will increment the major version, e.g.Remain forward-compatible with future minor versions. Ignore any object properties with unrecognized names to "1.1", for backward-compatibleĬhanges or additions. We will increment the minor version, e.g.The output includes a format_version key, which as of Terraform 1.1.0 has See the terraform show documentation for more details. Use terraform show -json to generate a JSON representation of a plan or state file. It can also convert state files to the same format, to simplify data loading and provide better long-term compatibility. Since the format of plan files isn't suited for use with external tools (and likely never will be), Terraform can output a machine-readable JSON representation of a plan file's changes. It can also, when run with -out=, write a much more detailed binary plan file, which can later be used to apply those changes. When Terraform plans to make changes, it prints a human-readable summary to the terminal. Note: This format is available in Terraform 0.12 and later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |