This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-633 Remove namespace flag from token reset and deprecated code #284
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
recharte
changed the title
ghost
reviewed
Feb 8, 2024
ghost
approved these changes
Feb 8, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Remove namespace flag from token reset and deprecated code
Problem:
EVEREST-633
We are now forcing install to the percona-everest namespace it makes no sense to keep the namespace flag on the token reset command.
I also removed all code the code from the deprecated DB-related commands because after the BE updates it was breaking the build.
CHECKLIST
Jira
Tests