ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/internal/command/testdata/show-json/nested-modules/output.json

96 lines
2.5 KiB
JSON
Raw Normal View History

command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
{
json-output: Release format version 1.0
2021-09-01 17:17:13 +02:00
"format_version": "1.0",
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
"planned_values": {
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"root_module": {
"child_modules": [
{
"address": "module.my_module",
"child_modules": [
{
"resources": [
{
"address": "module.my_module.module.more.test_instance.test",
"mode": "managed",
"type": "test_instance",
"name": "test",
Mildwonkey/command tests (#24535) * command: refactor testBackendState to write states.State testBackendState was using the older terraform.State format, which is no longer sufficient for most tests since the state upgrader does not encode provider FQNs automatically. Users will run `terraform 0.13upgrade` to update their state to include provider FQNs in resources, but tests need to use the modern state format instead of relying on the automatic upgrade. * plan tests passing * graph tests passing * json packages test update * command test updates * update show test fixtures * state show tests passing
2020-04-02 18:58:44 +02:00
"provider_name": "registry.terraform.io/hashicorp/test",
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"schema_version": 0,
"values": {
"ami": "bar-var"
jsonplan and jsonstate: include sensitive_values in state representations (#28889) * jsonplan and jsonstate: include sensitive_values in state representations A sensitive_values field has been added to the resource in state and planned values which is a map of all sensitive attributes with the values set to true. It wasn't entirely clear to me if the values in state would suffice, or if we also need to consult the schema - I believe that this is sufficient for state files written since v0.15, and if that's incorrect or insufficient, I'll add in the provider schema check as well. I also updated the documentation, and, since we've considered this before, bumped the FormatVersions for both jsonstate and jsonplan.
2021-06-14 15:19:13 +02:00
},
"sensitive_values": {}
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
}
],
"address": "module.my_module.module.more"
}
]
}
]
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
},
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"resource_changes": [
{
"address": "module.my_module.module.more.test_instance.test",
"module_address": "module.my_module.module.more",
"mode": "managed",
"type": "test_instance",
"name": "test",
Mildwonkey/command tests (#24535) * command: refactor testBackendState to write states.State testBackendState was using the older terraform.State format, which is no longer sufficient for most tests since the state upgrader does not encode provider FQNs automatically. Users will run `terraform 0.13upgrade` to update their state to include provider FQNs in resources, but tests need to use the modern state format instead of relying on the automatic upgrade. * plan tests passing * graph tests passing * json packages test update * command test updates * update show test fixtures * state show tests passing
2020-04-02 18:58:44 +02:00
"provider_name": "registry.terraform.io/hashicorp/test",
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"change": {
"actions": [
"create"
],
"before": null,
"after": {
"ami": "bar-var"
},
"after_unknown": {
"id": true
command/jsonplan: Add sensitive value mapping data Similar to `after_unknown`, `before_sensitive` and `after_sensitive` are values with similar structure to `before` and `after` which encode the presence of sensitive values in a planned change. These should be used to obscure sensitive values from human-readable output. These values follow the same structure as the `before` and `after` values, replacing sensitive values with `true`, and non-sensitive values with `false`. Following the `after_unknown` precedent, we omit non-sensitive `false` values for object attributes/map values, to make serialization more compact. One difference from `after_unknown` is that a sensitive complex value (collection or structural type) is replaced with `true`. If the complex value itself is sensitive, all of its contents should be obscured.
2021-03-25 16:41:49 +01:00
},
"after_sensitive": {},
"before_sensitive": false
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
}
}
],
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
"configuration": {
"root_module": {
"module_calls": {
"my_module": {
"source": "./modules",
"module": {
command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
"module_calls": {
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
"more": {
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"source": "./more-modules",
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
"module": {
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"resources": [
{
"address": "test_instance.test",
"mode": "managed",
"type": "test_instance",
"name": "test",
jsonconfig: Improve provider configuration output When rendering configuration as JSON, we have a single map of provider configurations at the top level, since these are globally applicable. Each resource has an opaque key into this map which points at the configuration data for the provider. This commit fixes two bugs in this implementation: - Resources in non-root modules had an invalid provider config key, which meant that there was never a valid reference to the provider config block. These keys were prefixed with the local module name instead of the path to the module. This is now corrected. - Modules with passed provider configs would point to either an empty provider config block or one which is not present at all. This has been fixed so that these resources point to the provider config block from the calling module (or wherever up the module tree it was originally defined). We also add a "full_name" key-value pair to the provider config block, with the entire fully-qualified provider name including hostname and namespace.
2021-12-10 18:48:32 +01:00
"provider_config_key": "module.my_module.module.more:test",
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"expressions": {
"ami": {
"references": [
"var.test_var"
]
}
},
"schema_version": 0
}
],
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
"variables": {
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
"test_var": {
"default": "bar-var"
command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
}
command/jsonplan: fix bug with nested modules output (#23092) `marshalPlannedValues` builds a map of modules to their children in order to output the resource changes in a tree. The map was built from the list of resource changes. However if a module had no resources itself, and only called another module (a very normal case), that module would not get added to the map causing none of its children to be output in `planned_values`. This PR adds a walk up through a given module's ancestors to ensure that each module, even those without resources, would be added.
2019-10-17 17:33:04 +02:00
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
}
command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
}
command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
}
command/show (-json): fix panic if a moduleCall has a nil config In the unlikely event that a moduleCall has a nil config - for example, if a nested module call includes a variable with a typo in an attribute - continue gracefully.
2019-06-03 17:19:03 +02:00
}
fix show-json test to expect error from nested mod One of the show json command tests expected no error when presented with an invalid configuration in a nested module. Modify the test created in PR #21569 so that it can still verify there is no panic, but now expect an error from init.
2019-07-17 03:25:30 +02:00
}
Mildwonkey/command tests (#24535) * command: refactor testBackendState to write states.State testBackendState was using the older terraform.State format, which is no longer sufficient for most tests since the state upgrader does not encode provider FQNs automatically. Users will run `terraform 0.13upgrade` to update their state to include provider FQNs in resources, but tests need to use the modern state format instead of relying on the automatic upgrade. * plan tests passing * graph tests passing * json packages test update * command test updates * update show test fixtures * state show tests passing
2020-04-02 18:58:44 +02:00
}