feat: add configuration validation for YAML config files #144
+960
−45
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
Signed-off-by: yogiboy1 <[email protected]>
yogiboy1
force-pushed
the
feature/113-add-config-validation
branch
from
fdd684a to
a1fcb2e
Compare
Signed-off-by: yogiboy1 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Describe what this change achieves.
This PR adds a validation script to automatically verify the structure and correctness of OpenSearch MCP Python configuration YAML files. The script ensures that configuration files follow the expected schema and helps prevent misconfigurations or runtime failures during MCP server initialization.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Closes #139
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.