-
Notifications
You must be signed in to change notification settings - Fork 232
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
helper/schema: Additional validation for schema attribute references #407
helper/schema: Additional validation for schema attribute references #407
Conversation
…onflictsWith and list index/map key syntax Reference: hashicorp#71 Reference: bflad/tfproviderlint#104 The `TestSchemaMap_InternalValidate` tests also include TODOs for potential schema validation improvements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bflad Can the fix be backported to V1 so those TODOs can be switched to Err: true
? I don't see it as a breaking change but rather a bugfix?
@appilon sure thing, I'll submit another PR after rebasing this one so the difference is super easy to replicate. 👍 |
v1-maint pull request with cherry-picked commits 👍 #416 |
…OneOf/ExactlyOneOf Reference: hashicorp#407 Reference: hashicorp#416 Includes TODO items for logic that needs adjustment to work as expected. `AtLeastOneOf` and `ExactlyOneOf` at the attribute level should not only allow self-reference, but also require it.
…ExactlyOneOf in InternalValidate Reference: hashicorp#407 Reference: hashicorp#416
…OneOf/ExactlyOneOf Reference: hashicorp#407 Reference: hashicorp#416 Includes TODO items for logic that needs adjustment to work as expected. `AtLeastOneOf` and `ExactlyOneOf` at the attribute level should not only allow self-reference, but also require it.
…ExactlyOneOf in InternalValidate Reference: hashicorp#407 Reference: hashicorp#416
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. |
Rebased #365
Reference: #71
Builds on testing from #364 (targeting v1). This PR currently targets v2.