Add boolean to the TopicOverview Object #1598
Merged
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
…ated directly on an environment or only promoted into that environment. Signed-off-by: Aindriu Lavelle <aindriu.lavelle@aiven.io>
Signed-off-by: Aindriu Lavelle <aindriu.lavelle@aiven.io>
programmiri
previously approved these changes
Aug 11, 2023
Signed-off-by: Aindriu Lavelle <aindriu.lavelle@aiven.io>
aindriu-aiven
dismissed stale reviews from muralibasani and programmiri
via
f953f95
programmiri
approved these changes
Aug 11, 2023
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.
Add boolean at TopicOverview level to indicate if a schema can be created directly on an environment or only promoted into that environment.
This means we are now able to determine even on a Topic that has no schema yet what environments allow a new schema to be created directly on them and which are restricted environments from a schema prespective.
About this change - What it does
Resolves: #xxxxx
Why this way