-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
SetNewCompute ipv6 attrs in vpc when added #8181
Conversation
If assign_generated_ipv6_block changes in a vpc, the diff has to reflect that the ipv6 attrs are going to change.
Hmm this appears related to #6721, but I had tagged it to wait until after the 0.12 SDK was merged in. Let me try to remember why. |
Oh, I missed that one, I only saw the upstream PR. I was in the area testing a recent SDK change, and thought I commit this update, but take whichever you prefer 👍 |
Ah yes, because the Terraform Provider SDK change was never backported to v0.11, so we don't want to merge failing testing:
|
Looks like this is nearly identical. I'll leave the existing PR for merging later. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
If
assign_generated_ipv6_block
changes in a vpc, the diff has to reflectthat the ipv6 attrs are going to change.
As is often the case,
diffs didn't match during apply
(soon to beProvider produced inconsistent final plan
) errors are caused by an upstream dependency. Here, a resource referencing the generatedipv6_cidr_block
will get the incorrect value if it changes during apply.Fixes #6710