Closed mbevc1 closed 3 years ago
This is working as intended. The variable sensitivity declared in the configuration defers to Terraform Cloud when variables are marked as sensitive there, with a bias to retain sensitivity.
The limitations of what you can do with sensitive values, even as they are transformed to something unsensitive, is understandable though - and this may be a use case to note for https://github.com/hashicorp/terraform/pull/27341
Cool, thanks!
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 Version
Terraform Configuration Files
Expected Behavior
When marking a variable in TFC as sensitive and passing value down in the code when executing it should obey
sensitive
setting invariables.tf
.Actual Behavior
sensitive
attribute is overridden and variable marked as sensitive, thus breaking code infor_each
loops.Steps to Reproduce
sensitive = false
for_each
loopfor_each
loopsAdditional Context
Examining this behaviour and more testing showed even if not using explicit sensitive value it's still masked in
plan
as sensitive value and it should succeed, which it did in previous versions. Is this intended behaviour?