[Bug]: aws_cloudformation_stack outputs disappear when using sensitive parameters #33327
Labels
bug
Addresses a defect in current functionality.
prioritized
Part of the maintainer teams immediate focus. To be addressed within the current quarter.
regression
Pertains to a degraded workflow resulting from an upstream patch or internal enhancement.
service/cloudformation
Issues and PRs that pertain to the cloudformation service.
Milestone
Terraform Core Version
1.5.6
AWS Provider Version
5.13.0,5.14.0,5.15.0
Affected Resource(s)
Expected Behavior
Apply with no error.
Actual Behavior
Error during apply.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Should apply cleanly
There will show an "update in place" to the cloudformation stack due to the sensitive parameter. But the cloudformation stack doesn't actually change, and has an empty output map.
Debug Output
No response
Panic Output
No response
Important Factoids
I've cut this down to use a sensitive file as the source of sensitive data, but it would equally apply to secrets read from SSM or some other sensitive source (random_secret or anything like that)
References
This is possibly a side-effect from the change in #33059
Pinning to 5.12.0 is a workaround for the moment.
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: