-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Using template output fails because of unknown value #2744
Comments
@thegedge theorizes this because route53 uses 'TypeSet' instead of 'TypeList' |
Hey @dalehamel. Thanks! Can you give us a sample TF config that triggers this? Thanks! |
@mitchellh this is the most minimal example I could produce
it generates a plan like this:
Notice how the records all have the "unknown value" of 74D93920-ED26-11E3-AC10-0800200C9A66? This will cause the diff sanity check to fail. |
Got it, thanks @dalehamel |
terraform: splatting with computed values is computed [GH-2744]
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. |
I am using the output of a template to get a dns record value.
When I try to change the count on that template, it will put the unknown value in the diff:
This then fails to apply with the message:
Now that the value is known, because the template resource actually exists, if I run a plan:
It's able to actually GET the value, and it actually applies.
@phinze any idea how this can be fixed? Maybe we just need to teach the 'apply diffs must match' check resolve unknown values rather than crying?
The text was updated successfully, but these errors were encountered: