2020-03-05 14:13:45 +01:00
|
|
|
{
|
2021-09-09 17:25:35 +02:00
|
|
|
"format_version": "0.2",
|
2020-03-05 14:13:45 +01:00
|
|
|
"terraform_version": "0.13.0",
|
|
|
|
|
"variables": {
|
|
|
|
|
"test_var": {
|
|
|
|
|
"value": "bar"
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"planned_values": {
|
|
|
|
|
"outputs": {
|
|
|
|
|
"test": {
|
|
|
|
|
"sensitive": false,
|
|
|
|
|
"value": "bar"
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"root_module": {
|
|
|
|
|
"resources": [
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test[0]",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
|
|
|
|
"index": 0,
|
2020-04-02 18:58:44 +02:00
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
2020-03-05 14:13:45 +01:00
|
|
|
"schema_version": 0,
|
|
|
|
|
"values": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
2021-06-14 15:19:13 +02:00
|
|
|
},
|
|
|
|
|
"sensitive_values": {}
|
2020-03-05 14:13:45 +01:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test[1]",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
|
|
|
|
"index": 1,
|
2020-04-02 18:58:44 +02:00
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
2020-03-05 14:13:45 +01:00
|
|
|
"schema_version": 0,
|
|
|
|
|
"values": {
|
|
|
|
|
"ami": "bar"
|
2021-06-14 15:19:13 +02:00
|
|
|
},
|
|
|
|
|
"sensitive_values": {}
|
2020-03-05 14:13:45 +01:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
},
|
2021-06-17 20:32:47 +02:00
|
|
|
"resource_drift": [
|
|
|
|
|
{
|
core: refactoring.ImpliedMoveStatements replaces NodeCountBoundary
Going back a long time we've had a special magic behavior which tries to
recognize a situation where a module author either added or removed the
"count" argument from a resource that already has instances, and to
silently rename the zeroth or no-key instance so that we don't plan to
destroy and recreate the associated object.
Now we have a more general idea of "move statements", and specifically
the idea of "implied" move statements which replicates the same heuristic
we used to use for this behavior, we can treat this magic renaming rule as
just another "move statement", special only in that Terraform generates it
automatically rather than it being written out explicitly in the
configuration.
In return for wiring that in, we can now remove altogether the
NodeCountBoundary graph node type and its associated graph transformer,
CountBoundaryTransformer. We handle moves as a preprocessing step before
building the plan graph, so we no longer need to include any special nodes
in the graph to deal with that situation.
The test updates here are mainly for the graph builders themselves, to
acknowledge that indeed we're no longer inserting the NodeCountBoundary
vertices. The vertices that NodeCountBoundary previously depended on now
become dependencies of the special "root" vertex, although in many cases
here we don't see that explicitly because of the transitive reduction
algorithm, which notices when there's already an equivalent indirect
dependency chain and removes the redundant edge.
We already have plenty of test coverage for these "count boundary" cases
in the context tests whose names start with TestContext2Plan_count and
TestContext2Apply_resourceCount, all of which continued to pass here
without any modification and so are not visible in the diff. The test
functions particularly relevant to this situation are:
- TestContext2Plan_countIncreaseFromNotSet
- TestContext2Plan_countDecreaseToOne
- TestContext2Plan_countOneIndex
- TestContext2Apply_countDecreaseToOneCorrupted
The last of those in particular deals with the situation where we have
both a no-key instance _and_ a zero-key instance in the prior state, which
is interesting here because to exercises an intentional interaction
between refactoring.ImpliedMoveStatements and refactoring.ApplyMoves,
where we intentionally generate an implied move statement that produces
a collision and then expect ApplyMoves to deal with it in the same way as
it would deal with all other collisions, and thus ensure we handle both
the explicit and implied collisions in the same way.
This does affect some UI-level tests, because a nice side-effect of this
new treatment of this old feature is that we can now report explicitly
in the UI that we're assigning new addresses to these objects, whereas
before we just said nothing and hoped the user would just guess what had
happened and why they therefore weren't seeing a diff.
The backend/local plan tests actually had a pre-existing bug where they
were using a state with a different instance key than the config called
for but getting away with it because we'd previously silently fix it up.
That's still fixed up, but now done with an explicit mention in the UI
and so I made the state consistent with the configuration here so that the
tests would be able to recognize _real_ differences where present, as
opposed to the errant difference caused by that inconsistency.
2021-09-18 00:32:32 +02:00
|
|
|
"address": "test_instance.test[0]",
|
2021-06-17 20:32:47 +02:00
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
|
|
|
|
"name": "test",
|
core: refactoring.ImpliedMoveStatements replaces NodeCountBoundary
Going back a long time we've had a special magic behavior which tries to
recognize a situation where a module author either added or removed the
"count" argument from a resource that already has instances, and to
silently rename the zeroth or no-key instance so that we don't plan to
destroy and recreate the associated object.
Now we have a more general idea of "move statements", and specifically
the idea of "implied" move statements which replicates the same heuristic
we used to use for this behavior, we can treat this magic renaming rule as
just another "move statement", special only in that Terraform generates it
automatically rather than it being written out explicitly in the
configuration.
In return for wiring that in, we can now remove altogether the
NodeCountBoundary graph node type and its associated graph transformer,
CountBoundaryTransformer. We handle moves as a preprocessing step before
building the plan graph, so we no longer need to include any special nodes
in the graph to deal with that situation.
The test updates here are mainly for the graph builders themselves, to
acknowledge that indeed we're no longer inserting the NodeCountBoundary
vertices. The vertices that NodeCountBoundary previously depended on now
become dependencies of the special "root" vertex, although in many cases
here we don't see that explicitly because of the transitive reduction
algorithm, which notices when there's already an equivalent indirect
dependency chain and removes the redundant edge.
We already have plenty of test coverage for these "count boundary" cases
in the context tests whose names start with TestContext2Plan_count and
TestContext2Apply_resourceCount, all of which continued to pass here
without any modification and so are not visible in the diff. The test
functions particularly relevant to this situation are:
- TestContext2Plan_countIncreaseFromNotSet
- TestContext2Plan_countDecreaseToOne
- TestContext2Plan_countOneIndex
- TestContext2Apply_countDecreaseToOneCorrupted
The last of those in particular deals with the situation where we have
both a no-key instance _and_ a zero-key instance in the prior state, which
is interesting here because to exercises an intentional interaction
between refactoring.ImpliedMoveStatements and refactoring.ApplyMoves,
where we intentionally generate an implied move statement that produces
a collision and then expect ApplyMoves to deal with it in the same way as
it would deal with all other collisions, and thus ensure we handle both
the explicit and implied collisions in the same way.
This does affect some UI-level tests, because a nice side-effect of this
new treatment of this old feature is that we can now report explicitly
in the UI that we're assigning new addresses to these objects, whereas
before we just said nothing and hoped the user would just guess what had
happened and why they therefore weren't seeing a diff.
The backend/local plan tests actually had a pre-existing bug where they
were using a state with a different instance key than the config called
for but getting away with it because we'd previously silently fix it up.
That's still fixed up, but now done with an explicit mention in the UI
and so I made the state consistent with the configuration here so that the
tests would be able to recognize _real_ differences where present, as
opposed to the errant difference caused by that inconsistency.
2021-09-18 00:32:32 +02:00
|
|
|
"index": 0,
|
2021-06-17 20:32:47 +02:00
|
|
|
"change": {
|
|
|
|
|
"actions": [
|
core: refactoring.ImpliedMoveStatements replaces NodeCountBoundary
Going back a long time we've had a special magic behavior which tries to
recognize a situation where a module author either added or removed the
"count" argument from a resource that already has instances, and to
silently rename the zeroth or no-key instance so that we don't plan to
destroy and recreate the associated object.
Now we have a more general idea of "move statements", and specifically
the idea of "implied" move statements which replicates the same heuristic
we used to use for this behavior, we can treat this magic renaming rule as
just another "move statement", special only in that Terraform generates it
automatically rather than it being written out explicitly in the
configuration.
In return for wiring that in, we can now remove altogether the
NodeCountBoundary graph node type and its associated graph transformer,
CountBoundaryTransformer. We handle moves as a preprocessing step before
building the plan graph, so we no longer need to include any special nodes
in the graph to deal with that situation.
The test updates here are mainly for the graph builders themselves, to
acknowledge that indeed we're no longer inserting the NodeCountBoundary
vertices. The vertices that NodeCountBoundary previously depended on now
become dependencies of the special "root" vertex, although in many cases
here we don't see that explicitly because of the transitive reduction
algorithm, which notices when there's already an equivalent indirect
dependency chain and removes the redundant edge.
We already have plenty of test coverage for these "count boundary" cases
in the context tests whose names start with TestContext2Plan_count and
TestContext2Apply_resourceCount, all of which continued to pass here
without any modification and so are not visible in the diff. The test
functions particularly relevant to this situation are:
- TestContext2Plan_countIncreaseFromNotSet
- TestContext2Plan_countDecreaseToOne
- TestContext2Plan_countOneIndex
- TestContext2Apply_countDecreaseToOneCorrupted
The last of those in particular deals with the situation where we have
both a no-key instance _and_ a zero-key instance in the prior state, which
is interesting here because to exercises an intentional interaction
between refactoring.ImpliedMoveStatements and refactoring.ApplyMoves,
where we intentionally generate an implied move statement that produces
a collision and then expect ApplyMoves to deal with it in the same way as
it would deal with all other collisions, and thus ensure we handle both
the explicit and implied collisions in the same way.
This does affect some UI-level tests, because a nice side-effect of this
new treatment of this old feature is that we can now report explicitly
in the UI that we're assigning new addresses to these objects, whereas
before we just said nothing and hoped the user would just guess what had
happened and why they therefore weren't seeing a diff.
The backend/local plan tests actually had a pre-existing bug where they
were using a state with a different instance key than the config called
for but getting away with it because we'd previously silently fix it up.
That's still fixed up, but now done with an explicit mention in the UI
and so I made the state consistent with the configuration here so that the
tests would be able to recognize _real_ differences where present, as
opposed to the errant difference caused by that inconsistency.
2021-09-18 00:32:32 +02:00
|
|
|
"no-op"
|
2021-06-17 20:32:47 +02:00
|
|
|
],
|
|
|
|
|
"before": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
|
|
|
|
},
|
core: refactoring.ImpliedMoveStatements replaces NodeCountBoundary
Going back a long time we've had a special magic behavior which tries to
recognize a situation where a module author either added or removed the
"count" argument from a resource that already has instances, and to
silently rename the zeroth or no-key instance so that we don't plan to
destroy and recreate the associated object.
Now we have a more general idea of "move statements", and specifically
the idea of "implied" move statements which replicates the same heuristic
we used to use for this behavior, we can treat this magic renaming rule as
just another "move statement", special only in that Terraform generates it
automatically rather than it being written out explicitly in the
configuration.
In return for wiring that in, we can now remove altogether the
NodeCountBoundary graph node type and its associated graph transformer,
CountBoundaryTransformer. We handle moves as a preprocessing step before
building the plan graph, so we no longer need to include any special nodes
in the graph to deal with that situation.
The test updates here are mainly for the graph builders themselves, to
acknowledge that indeed we're no longer inserting the NodeCountBoundary
vertices. The vertices that NodeCountBoundary previously depended on now
become dependencies of the special "root" vertex, although in many cases
here we don't see that explicitly because of the transitive reduction
algorithm, which notices when there's already an equivalent indirect
dependency chain and removes the redundant edge.
We already have plenty of test coverage for these "count boundary" cases
in the context tests whose names start with TestContext2Plan_count and
TestContext2Apply_resourceCount, all of which continued to pass here
without any modification and so are not visible in the diff. The test
functions particularly relevant to this situation are:
- TestContext2Plan_countIncreaseFromNotSet
- TestContext2Plan_countDecreaseToOne
- TestContext2Plan_countOneIndex
- TestContext2Apply_countDecreaseToOneCorrupted
The last of those in particular deals with the situation where we have
both a no-key instance _and_ a zero-key instance in the prior state, which
is interesting here because to exercises an intentional interaction
between refactoring.ImpliedMoveStatements and refactoring.ApplyMoves,
where we intentionally generate an implied move statement that produces
a collision and then expect ApplyMoves to deal with it in the same way as
it would deal with all other collisions, and thus ensure we handle both
the explicit and implied collisions in the same way.
This does affect some UI-level tests, because a nice side-effect of this
new treatment of this old feature is that we can now report explicitly
in the UI that we're assigning new addresses to these objects, whereas
before we just said nothing and hoped the user would just guess what had
happened and why they therefore weren't seeing a diff.
The backend/local plan tests actually had a pre-existing bug where they
were using a state with a different instance key than the config called
for but getting away with it because we'd previously silently fix it up.
That's still fixed up, but now done with an explicit mention in the UI
and so I made the state consistent with the configuration here so that the
tests would be able to recognize _real_ differences where present, as
opposed to the errant difference caused by that inconsistency.
2021-09-18 00:32:32 +02:00
|
|
|
"after": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
|
|
|
|
},
|
2021-06-17 20:32:47 +02:00
|
|
|
"before_sensitive": {},
|
core: refactoring.ImpliedMoveStatements replaces NodeCountBoundary
Going back a long time we've had a special magic behavior which tries to
recognize a situation where a module author either added or removed the
"count" argument from a resource that already has instances, and to
silently rename the zeroth or no-key instance so that we don't plan to
destroy and recreate the associated object.
Now we have a more general idea of "move statements", and specifically
the idea of "implied" move statements which replicates the same heuristic
we used to use for this behavior, we can treat this magic renaming rule as
just another "move statement", special only in that Terraform generates it
automatically rather than it being written out explicitly in the
configuration.
In return for wiring that in, we can now remove altogether the
NodeCountBoundary graph node type and its associated graph transformer,
CountBoundaryTransformer. We handle moves as a preprocessing step before
building the plan graph, so we no longer need to include any special nodes
in the graph to deal with that situation.
The test updates here are mainly for the graph builders themselves, to
acknowledge that indeed we're no longer inserting the NodeCountBoundary
vertices. The vertices that NodeCountBoundary previously depended on now
become dependencies of the special "root" vertex, although in many cases
here we don't see that explicitly because of the transitive reduction
algorithm, which notices when there's already an equivalent indirect
dependency chain and removes the redundant edge.
We already have plenty of test coverage for these "count boundary" cases
in the context tests whose names start with TestContext2Plan_count and
TestContext2Apply_resourceCount, all of which continued to pass here
without any modification and so are not visible in the diff. The test
functions particularly relevant to this situation are:
- TestContext2Plan_countIncreaseFromNotSet
- TestContext2Plan_countDecreaseToOne
- TestContext2Plan_countOneIndex
- TestContext2Apply_countDecreaseToOneCorrupted
The last of those in particular deals with the situation where we have
both a no-key instance _and_ a zero-key instance in the prior state, which
is interesting here because to exercises an intentional interaction
between refactoring.ImpliedMoveStatements and refactoring.ApplyMoves,
where we intentionally generate an implied move statement that produces
a collision and then expect ApplyMoves to deal with it in the same way as
it would deal with all other collisions, and thus ensure we handle both
the explicit and implied collisions in the same way.
This does affect some UI-level tests, because a nice side-effect of this
new treatment of this old feature is that we can now report explicitly
in the UI that we're assigning new addresses to these objects, whereas
before we just said nothing and hoped the user would just guess what had
happened and why they therefore weren't seeing a diff.
The backend/local plan tests actually had a pre-existing bug where they
were using a state with a different instance key than the config called
for but getting away with it because we'd previously silently fix it up.
That's still fixed up, but now done with an explicit mention in the UI
and so I made the state consistent with the configuration here so that the
tests would be able to recognize _real_ differences where present, as
opposed to the errant difference caused by that inconsistency.
2021-09-18 00:32:32 +02:00
|
|
|
"after_sensitive": {},
|
2021-09-13 23:30:16 +02:00
|
|
|
"after_unknown": {}
|
2021-06-17 20:32:47 +02:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
],
|
2020-03-05 14:13:45 +01:00
|
|
|
"resource_changes": [
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test[0]",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
|
|
|
|
"index": 0,
|
2020-04-02 18:58:44 +02:00
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
2020-03-05 14:13:45 +01:00
|
|
|
"change": {
|
|
|
|
|
"actions": [
|
|
|
|
|
"no-op"
|
|
|
|
|
],
|
|
|
|
|
"before": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
|
|
|
|
},
|
|
|
|
|
"after": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
|
|
|
|
},
|
2021-03-25 16:41:49 +01:00
|
|
|
"after_unknown": {},
|
|
|
|
|
"after_sensitive": {},
|
|
|
|
|
"before_sensitive": {}
|
2020-03-05 14:13:45 +01:00
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test[1]",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
|
|
|
|
"index": 1,
|
2020-04-02 18:58:44 +02:00
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
2020-03-05 14:13:45 +01:00
|
|
|
"change": {
|
|
|
|
|
"actions": [
|
|
|
|
|
"create"
|
|
|
|
|
],
|
|
|
|
|
"before": null,
|
|
|
|
|
"after": {
|
|
|
|
|
"ami": "bar"
|
|
|
|
|
},
|
|
|
|
|
"after_unknown": {
|
|
|
|
|
"id": true
|
2021-03-25 16:41:49 +01:00
|
|
|
},
|
|
|
|
|
"after_sensitive": {},
|
|
|
|
|
"before_sensitive": false
|
2020-03-05 14:13:45 +01:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
"output_changes": {
|
|
|
|
|
"test": {
|
|
|
|
|
"actions": [
|
2020-10-10 01:45:31 +02:00
|
|
|
"no-op"
|
2020-03-05 14:13:45 +01:00
|
|
|
],
|
2020-10-10 01:45:31 +02:00
|
|
|
"before": "bar",
|
2020-03-05 14:13:45 +01:00
|
|
|
"after": "bar",
|
2021-03-27 00:21:40 +01:00
|
|
|
"after_unknown": false,
|
|
|
|
|
"before_sensitive": false,
|
|
|
|
|
"after_sensitive": false
|
2020-03-05 14:13:45 +01:00
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"prior_state": {
|
2021-09-09 17:25:35 +02:00
|
|
|
"format_version": "0.2",
|
2020-03-05 14:13:45 +01:00
|
|
|
"terraform_version": "0.13.0",
|
|
|
|
|
"values": {
|
2020-09-21 20:39:25 +02:00
|
|
|
"outputs": {
|
|
|
|
|
"test": {
|
|
|
|
|
"sensitive": false,
|
|
|
|
|
"value": "bar"
|
|
|
|
|
}
|
|
|
|
|
},
|
2020-03-05 14:13:45 +01:00
|
|
|
"root_module": {
|
|
|
|
|
"resources": [
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test[0]",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
2020-09-21 20:39:25 +02:00
|
|
|
"index": 0,
|
2020-04-02 18:58:44 +02:00
|
|
|
"provider_name": "registry.terraform.io/hashicorp/test",
|
2020-03-05 14:13:45 +01:00
|
|
|
"schema_version": 0,
|
|
|
|
|
"values": {
|
|
|
|
|
"ami": "bar",
|
|
|
|
|
"id": "placeholder"
|
2021-06-14 15:19:13 +02:00
|
|
|
},
|
|
|
|
|
"sensitive_values": {}
|
2020-03-05 14:13:45 +01:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"configuration": {
|
|
|
|
|
"root_module": {
|
|
|
|
|
"outputs": {
|
|
|
|
|
"test": {
|
|
|
|
|
"expression": {
|
|
|
|
|
"references": [
|
|
|
|
|
"var.test_var"
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"resources": [
|
|
|
|
|
{
|
|
|
|
|
"address": "test_instance.test",
|
|
|
|
|
"mode": "managed",
|
|
|
|
|
"type": "test_instance",
|
|
|
|
|
"name": "test",
|
|
|
|
|
"provider_config_key": "test",
|
|
|
|
|
"expressions": {
|
|
|
|
|
"ami": {
|
|
|
|
|
"references": [
|
|
|
|
|
"var.test_var"
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"schema_version": 0,
|
|
|
|
|
"count_expression": {
|
|
|
|
|
"constant_value": 2
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
],
|
|
|
|
|
"variables": {
|
|
|
|
|
"test_var": {
|
|
|
|
|
"default": "bar"
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|