Files
opentf/testing/equivalence-tests/outputs/nested_objects_update/plan
Martin Atkins 15272f8672 plan diff: summarize the current -> planned notation
The human-oriented plan output includes a short summary of the meaning of
all of the different "icons" used to describe different kinds of change,
but nothing was previously describing how OpenTofu uses "->" to describe
the transition between current and planned values for update in-place, "~".

We'll now include a concise note about that as part of the icon summary,
keeping things still relatively compact but nonetheless giving something
to refer to if a reader is unsure about the meaning of this notation.

Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
2025-08-26 11:37:44 -07:00

32 lines
1.4 KiB
Plaintext

tfcoremock_nested_object.nested_object: Refreshing state... [id=B2491EF0-9361-40FD-B25A-0332A1A5E052]
OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place (current -> planned)
OpenTofu will perform the following actions:
# tfcoremock_nested_object.nested_object will be updated in-place
~ resource "tfcoremock_nested_object" "nested_object" {
id = "B2491EF0-9361-40FD-B25A-0332A1A5E052"
~ parent_object = {
~ first_nested_object = {
~ attribute_two = "5425587C-49EF-4C1E-A906-1DC923A12725" -> "FB350D92-4AAE-48C6-A408-BFFAFAD46B04"
# (1 unchanged attribute hidden)
}
~ second_nested_object = {
~ attribute_two = "FB350D92-4AAE-48C6-A408-BFFAFAD46B04" -> "5425587C-49EF-4C1E-A906-1DC923A12725"
# (1 unchanged attribute hidden)
}
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
─────────────────────────────────────────────────────────────────────────────
Saved the plan to: equivalence_test_plan
To perform exactly these actions, run the following command to apply:
tofu apply "equivalence_test_plan"