fix: return 422 for Avro/JSONSchema when payload does not match schema #853
Conversation
This file contains 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
jjaakola-aiven
force-pushed
the
jjaakola-aiven-rest-proxy-return-422-for-invalid-payload
branch
from
78b5fea to
0b8660a
Compare
jjaakola-aiven
force-pushed
the
jjaakola-aiven-rest-proxy-return-422-for-invalid-payload
branch
from
0b8660a to
76cab2d
Compare
tvainika
approved these changes
Apr 30, 2024
tvainika
deleted the
jjaakola-aiven-rest-proxy-return-422-for-invalid-payload
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
About this change - What it does
Karapace returned 500 error for JSON payload that did not match JSON schema when serialization format was
jsonschema.Added an integration test which tests also Avro schema and payload.