Fix cloudflare_access_policy requiring explictly either account id or zone id #3352
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
changelog detected ✅ |
GreenStage
force-pushed
the
egomes/fix-policy-accid
branch
from
9fd18e8 to
dcbdaaf
Compare
|
This functionality has been released in v4.35.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! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
on 4.34 I've introduced a bug by changing ConflictsWith to ExactlyOneOf. Some customers are still have some tf scripts without the account_id in the terraform policy, so it is now breaking.
I think we do not support omitting account_id in favor of CLOUDFLARE_ACCOUNT_ID anymore anyway, but that fails on create, not on validation for untouched resources.