-
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
Diff's didn't match during apply: associate_public_ip_address #7306
Comments
I'm not sure how this related, but while reproducing this, I made a change to an unrelated s3 bucket policy (in json) which resulted in the following error:
Somehow the JSON wasn't being rendered. When I tried it again, the problem went away. To be really clear, the JSON wasn't invalid, and I made no changes that resulted in it parsing correctly. |
This should be fixed in later versions of 0.7.x |
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
0.6.16
Affected Resource(s)
Terraform Configuration Files
This is happening from a module I wrote. You can see it here: https://github.com/rhettg/tf_aws_lab/blob/master/vpn.tf
Debug Output
https://gist.github.com/rhettg/40ce52f8ffaea3d3541f379bb1052a50
Expected Behavior
I wanted to replace the VPN instance, so I tainted it:
It should have destroyed it and recreated
Actual Behavior
The host was destroyed, but then I got the above error.
Retrying the command will create the new instance.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform taint -module=vpc_lab aws_instance.vpn
terraform apply
References
I think this is related to #5956
The text was updated successfully, but these errors were encountered: