Add error handling for unknown fields in orchestrator request #285
+51
−11
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.
Story: foundation-model-stack/fms-guardrails-orchestrator#261
What does your PR do?
This PR adds a container attribute from the serde framework to handle unknown fields passed into to a request for ochestrator APIs. A unit test is also added asserting the case used for the scenario used in the git issue.
How this was tested
In addition to the unit test, each endpoint was modified to have a field name with a typo, or an outright made up field, and compared with an older orchestrator version deployed on openshift, versus the locally modified version.
Example: