-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Change affected AtLeastOneOfs back to ExactlyOneOf #5193
Change affected AtLeastOneOfs back to ExactlyOneOf #5193
Comments
Hello ! Do you have a date for the availability of these new features? It is quite structuring on the firewall part etc.. |
The behavior of this should be correct as of GoogleCloudPlatform/magic-modules#2856. This specific issue is to simplify the code by having it be ExactlyOneOf instead of AtLeastOneOf+ConflictsWith. Are you seeing otherwise? I'm not totally sure from your comment what you mean by "it is quite structuring on the firewall part" |
Not sure if this is the right place to report this, but 3.20.0 seems to have reintroduced the issue described in hashicorp/terraform-plugin-sdk#280 that links to this issue. We ran into that same error signature today when applying |
Oh gosh, we never revendored the SDK after they fixed it on their end 🤦♀️ I'll go ahead and do that now for our next release. |
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
See #5024
This affects:
Because of hashicorp/terraform-plugin-sdk#280, several fields that were ExactlyOneOf were changed to AtLeastOneOf. In the next major release after the blocking issue is fixed, change them back.
The text was updated successfully, but these errors were encountered: