You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"example_set_nested_example""myExample" {
set = [
{
name ="test2"
bool_two =true
}
]
}
Debug Output
Expected Behavior
The provider would not produce any plan after the first apply.
Actual Behavior
The first apply succeeds, and everything looks right in the state. On every subsequent apply, the generated plan flips the bool_two value to its opposite value.
First plan for example:
# example_set_nested_example.myExample will be created
+ resource "example_set_nested_example" "myExample" {
+ set = [
+ {
+ bool_one = false
+ bool_two = true
+ name = "test2"
},
]
}
I believe this bug report is a different result of a similar root cause from #783 and #709, a known issue with Set identity and plan modification (default values).
I have been bitten by this. My workaround was to re-implement the defaults using a custom plan modifier on the set. I'll subscribe to this in hopes of removing that horrible cludge.
Module version
Relevant provider source code
Terraform Configuration Files
Debug Output
Expected Behavior
The provider would not produce any plan after the first apply.
Actual Behavior
The first apply succeeds, and everything looks right in the state. On every subsequent apply, the generated plan flips the
bool_two
value to its opposite value.First plan for example:
Second plan with no changes to HCL:
Third plan:
The plans will continue to cycle between setting
bool_two
to true and to false.Steps to Reproduce
Apply the provided HCL multiple times
The text was updated successfully, but these errors were encountered: