-
Notifications
You must be signed in to change notification settings - Fork 609
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
fix: mark verification key as computed when changing to or from partial zone type #4019
fix: mark verification key as computed when changing to or from partial zone type #4019
Conversation
…ial zone type Signed-off-by: Jon Carl <[email protected]>
changelog detected ✅ |
Signed-off-by: Jon Carl <[email protected]>
this has introduced a regression with the zone acceptance tests
|
Marking this pull request as stale due to 14 days of inactivity. This helps our maintainers find and focus on the active pull requests. If this pull request receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
50feb4a
to
76350e6
Compare
Signed-off-by: Jon Carl <[email protected]> (cherry picked from commit 50feb4a)
@jacobbednarz thanks for the info. I've updated the code and verified those acceptance tests now pass. |
nice one, thanks
|
This functionality has been released in v4.44.0 of the Terraform Cloudflare Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
When changing a zone to or from type
partial
thecloudflare_zone.<ID>.verification_key
will also change. However, the change is not reflected in the plan and thus any resources needing the value ofverification_key
won't pick up the change until the next apply. This is undesirable as you want to have the change reflected in one apply.This PR changes it so that when
type
changes to or frompartial
Terraform knows thatverification_key
will be changed as well.Before
Here's an example of before. As you can see when changing from
full
topartial
it did not show thatverification_key
was changing.On the next apply it picks up the change.
After
Here's what it looks like after: in the same apply that is changing from
full
topartial
it shows thatverification_key
will change. Then, when the apply completes the value is there. No second apply needed.