-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splat operator with sensitive values panics: "value is marked, so must be unmarked first" #27329
Comments
Thanks for the reproduction case, @woz5999! This is indeed another issue with unmarking sensitive values when evaluating expressions, and this time the splat is the problem here. We'll need to fix that again in the upstream HCL library. For now, you can replace the use of splat with a for expression, as you hinted at yourself. The following should be a reasonable workaround until we can get this fixed: locals {
fixed_crash_local = flatten([for kvs in local.a_sensitive_map: [for v in kvs: v]])
} |
Thanks @alisdair . Been refactoring and confirm that that's a fix. I'm seeing a few other cases, though I'm not sure how similar they are under the hood:
let me know if you want a new ticket for this, else i can update this one to include the additional case |
@woz5999 Thanks again. That is a separate crash, caused by checking the length of a sensitive collection (in |
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
Crash Output
Expected Behavior
Command Success
Actual Behavior
Panic / terraform crash
Steps to Reproduce
terraform init
terraform plan
Additional Context
References
The text was updated successfully, but these errors were encountered: