Allow transition from Deprecated state to Enabled or Disabled states #783
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
- This commit allows an artifact to transition from the `Deprecated` state to either the `Enabled` or `Disabled` states. This allows users who have accidentally deprecated a schema to re-enable it, or it allows a deprecated schema to become disabled so that clients can no longer use it. Signed-off-by: Andrew Borley <[email protected]>
EricWittmann
approved these changes
Aug 25, 2020
EricWittmann
added
Documentation
Impacts Documentation
|
Documented in #967 |
EricWittmann
removed
the
Impacts Documentation
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.
Deprecatedstate to either the
EnabledorDisabledstates. This allows userswho have accidentally deprecated a schema to re-enable it, or it allows
a deprecated schema to become disabled so that clients can no longer use
it.
See initial discussion in issue #722
Signed-off-by: Andrew Borley [email protected]