Add HTTP URI to SCHEMA_REGISTRY_URL #49
Merged
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
|
I think kafkactl should handle this okay? |
cultureamp-brucew
approved these changes
Oct 3, 2024
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.
Context
There are multiple Kafka libraries (e.g. Python, Ruby and Kotlin based) that expect the URL for schema registry to include the HTTP URI when querying schemas as part of handling Avro serialisation/deserialisation.
Teams expect to be able to use
SCHEMA_REGISTRY_URLdirectly without explicitly prependinghttp://, and this has caused some confusing errors.We should include the URI by default.
Changes
SCHEMA_REGISTRY_URLto includehttp://URISCHEMA_REGISTRY_URLto no longer require hard-codedhttp://