Makes the deprecated feature-flag warning more precise #723
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
luhi-DT
reviewed
Apr 14, 2022
chrismuellner
previously requested changes
Apr 15, 2022
meik99
suggested changes
Apr 21, 2022
meik99
approved these changes
Apr 21, 2022
0sewa0
added a commit
that referenced
this pull request
Apr 21, 2022
2 tasks
0sewa0
added a commit
that referenced
this pull request
Apr 22, 2022
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.
Description
The original message for the deprecated feature-flag warning was a bit vague. This adds a bit more context.
How can this be tested?
Delpoy a dynakube with a feature-flag that has a
alpha.prefix, and see the warning message in the command lineChecklist