-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
output_changes
incorrectly calculated in the plan file
#24628
Comments
Thanks for reporting this! If I'm reading this right, it looks like you're reporting an issue specific to the Please feel free to re-open this if I'm misunderstanding this and it is in fact a core issue. |
This issue has been automatically migrated to hashicorp/terraform-provider-random#110 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-random#110. |
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 believe this is a known Core issue, not an issue with the It is documented that "In the Terraform CLI 0.12.0 release, Terraform is not yet fully able to track changes to output values, so the actions indicated may not be fully accurate, but the "after" value will always be correct." |
Yes, I just reproduced this in https://github.com/hashicorp/terraform-cdk |
@skorfmann I made a reproduction of this here, and wasn't able to reproduce on master https://github.com/danieldreier/terraform-issue-reproductions/tree/master/24628 nor on the v0.14 branch. Could you help with a reproduction? |
I've tested https://github.com/danieldreier/terraform-issue-reproductions/tree/master/24628 with 0.12.29, 0.13.6, and 0.14.4. The former two versions show:
and 0.14.4 shows:
I therefore believe this bug was fixed somewhere between 0.13.6 and 0.14.4. I'd still like someone from Core to comment on the documentation: "In the Terraform CLI 0.12.0 release, Terraform is not yet fully able to track changes to output values, so the actions indicated may not be fully accurate, but the "after" value will always be correct." Is this still true? |
I am going to close this issue due to age. Also, as @kmoe has subsequently joined the Core team, if the question still needed an answer presumably it can now be found. :) |
Terraform Version
Terraform Configuration Files
Steps to reproduce
After the change has been applied:
Expected Behavior
The resulting JSON should set the value at
$.output_changes.bacon.before
to"7a9ae58d9bf9f18adec0d94c09c86440"
The resulting JSON should set the value at
$.output_changes.bacon.actions
to["no-op"]
Actual Behavior
The resulting JSON sets the value at
$.output_changes.bacon.before
tonull
The resulting JSON incorrectly sets the value at
$.output_changes.bacon.actions
to["create"]
The text was updated successfully, but these errors were encountered: