-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload schema from a secure schema registry #1299
Labels
feature
New feature
priority: high
Critical to the health of the project
request
External feature request
Comments
yruslan
added
feature
New feature
request
External feature request
priority: high
Critical to the health of the project
labels
Apr 23, 2020
dk1844
added a commit
that referenced
this issue
Jun 15, 2020
dk1844
added a commit
that referenced
this issue
Jun 17, 2020
dk1844
added a commit
that referenced
this issue
Jun 17, 2020
secure SR works by supplying keyStore & trustStore config values. Optionally, value+key can get combined, nontrivial combination for struct-based schemas added -> TODO add tests! menas template update with SR stuff SecureKafka.scala moved to utils and renamed to SecureConfig. Smart Pathjoining added via /.
dk1844
added a commit
that referenced
this issue
Jun 17, 2020
dk1844
added a commit
that referenced
this issue
Jun 17, 2020
dk1844
added a commit
that referenced
this issue
Jun 18, 2020
…accounted for, latest version of schema allowed to get fixed, e.g. `https://mydomain1.com/subjects/myTopic1/versions/latest` -> `https://mydomain1.com/subjects/myTopic1/versions/latest/schema`
dk1844
added a commit
that referenced
this issue
Jun 18, 2020
…st added. UI reset-after-schema-update fix (topicMergeWithKey)
dk1844
added a commit
that referenced
this issue
Jun 19, 2020
Release notes |
dk1844
added a commit
that referenced
this issue
Jun 22, 2020
dk1844
added a commit
that referenced
this issue
Jun 22, 2020
ConfigReader/ConfigImplicits consolidated a bit + unit tests added.
dk1844
added a commit
that referenced
this issue
Jun 24, 2020
…e api (upload, remoteUrl are always available for the user)
dk1844
added a commit
that referenced
this issue
Jun 24, 2020
…y subject is loaded + fallback subject-value. (unit-tests removed) - topicName -> subject rewording
dk1844
added a commit
that referenced
this issue
Jun 24, 2020
dk1844
added a commit
that referenced
this issue
Jun 24, 2020
dk1844
added a commit
that referenced
this issue
Jun 26, 2020
dk1844
added a commit
that referenced
this issue
Jun 29, 2020
dk1844
added a commit
that referenced
this issue
Jun 30, 2020
dk1844
added a commit
that referenced
this issue
Jul 7, 2020
* #1299 schema loading from schema registry by subjectName (or fallbacks to subjectName-value) - secure SR works by supplying keyStore & trustStore config values. - SecureKafka.scala moved to utils and renamed to SecureConfig. - Smart Pathjoining added via /. - UI update: vbox with collapsed/ible panels and formatted text with descriptions - SchemaApiFeature endpoint drives the SR integration enabling on UI - integration test added, unit tests added Co-authored-by: Saša Zejnilović <zejnils@gmail.com>
dk1844
added a commit
that referenced
this issue
Jul 7, 2020
dk1844
added a commit
that referenced
this issue
Jul 7, 2020
dk1844
added a commit
that referenced
this issue
Jul 7, 2020
dk1844
added a commit
that referenced
this issue
Jul 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature
New feature
priority: high
Critical to the health of the project
request
External feature request
Background
This is requested by our users as something that would be very helpful to them.
Feature
Upload schema from a secure schema registry.
@kevinwallimann gave a great idea how we can simplify all these things.
We should add support for specifying the subject of a schema registry.
The base URL of schema server should be configured in Menas in
application.properties
User should provide:
For the naming strategy based on the topic name it will betopic_name
-value
.[ ] An optional key subject might be specified (e.g.topic_name
-key
). If it is specified, the schema of the key should be merged with the value schema.topic_name
does not exist, there should be an automatic (behind the scenes) fallback totopic_name-value
. If even that does not succeed, the schema loading fails.Menas should:
The text was updated successfully, but these errors were encountered: