statestorevalidator: Add package for common statestore configuration validators#326
Open
statestorevalidator: Add package for common statestore configuration validators#326
Conversation
rainkwan
changed the title
austinvalle
approved these changes
Mar 2, 2026
Member
austinvalle
left a comment
austinvalle
left a comment
There was a problem hiding this comment.
Needs a rebase, but the changes here look good 👍🏻
Comment on lines
+7
to
+8
| github.com/hashicorp/terraform-plugin-framework v1.17.1-0.20260223163459-7b6eb103b2e8 | ||
| github.com/hashicorp/terraform-plugin-go v0.29.1-0.20260122204301-b0a6aca80fd7 |
Member
There was a problem hiding this comment.
If you rebase the PR I believe this change can disappear 😃
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR introduces a new statestorevalidator package that exposes the shared config validator implementations we already use for resource, action, provider config, etc.
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
No