test: Add test coverage for what validate command checks in resource blocks versus backend blocks. #37972
+125
−1
Conversation
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
SarahFrench
added
the
no-changelog-needed
…n validating backend blocks.
SarahFrench
force-pushed
the
sarah/investigate-validate-cmd
branch
from
bca1a9e to
83e3ac5
Compare
radeksimko
approved these changes
Dec 5, 2025
Member
radeksimko
left a comment
radeksimko
left a comment
There was a problem hiding this comment.
I don't think there was ever a good reason for not doing any schema-based validation for backends but I think there was probably a lot of caution related to the handling of empty strings and partial configuration.
We can almost certainly afford to be a bit braver with state stores though and try to do the validation there! 😄
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.
As part of identifying whether we need to make the validate command compatible with pluggable state storage I added some tests to characterise what the validate command checks for in backend blocks.
It turns out that resources are validated using their schemas, while backend blocks aren't validated using their schemas.
Target Release
N/A
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry