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
A more clear explanation as to what will change, so that this change can be approved properly.
Actual Behavior
Terraform only indicates the following:
Terraform will perform the following actions:
# random_string.rds_password will be updated in-place~ resource "random_string""rds_password" {
id = "REDACTED"# (11 unchanged attributes hidden)
}
Before and after there is a slight difference in the statefile (namely override_special and sensitive_attributes:
Hi @syphernl 👋 Thank you for raising this and apologies you ran into trouble here.
The provider unfortunately does not have any control about the plan difference output in this case as Terraform (due to some legacy reasons) is likely hiding the override_special attribute errantly going from null to "" with version 3.4.2.
The good news though is that this should be resolved by upgrading to 3.4.3, which was recently released. If the resource happened to be applied with 3.4.2, it may show one more plan to go from "" back to null then it'll stabilize. Additional reference: #312
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform CLI and Provider Versions
Terraform v1.2.9
on linux_amd64
Terraform Configuration
Expected Behavior
A more clear explanation as to what will change, so that this change can be approved properly.
Actual Behavior
Terraform only indicates the following:
Before and after there is a slight difference in the statefile (namely
override_special
andsensitive_attributes
:After:
Steps to Reproduce
terraform apply
on Random < 3.4.0terraform apply
on Random >= 3.4.0How much impact is this issue causing?
Low
Logs
No response
Additional Information
This could be related to #302
Code of Conduct
The text was updated successfully, but these errors were encountered: