Open caleb-gosnell opened 4 years ago
Also running into this issue. Lifecycle rules fix the problem but as @caleb-sixfeetup says, creates a different problem. The whole point of plan is to see what's going to change - makes no sense when there are dozens of false positives
I too can confirm this same behavior.
Terraform Version
Terraform v0.12.24
Affected Resource(s)
secured = true
Terraform Configuration Files
Expected Behavior
I only expect the value to be updated if it is changed, not on every apply.
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
terraform plan
Current Workaround
Avoid ever resetting the value, (opens the user up to a stale value):