EVEREST-1714 DB Creating status #1084
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
oksana-grishchenko
changed the title
4 tasks
maxkondr
approved these changes
Feb 6, 2025
oksana-grishchenko
merged commit efea456
into
EVEREST-1711-ui-remove-final-confirmation-step-from-the-wizard
11 checks passed
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.
EVEREST-1714
Problem:
The DB can be in an ‘unknown’ state for a couple of seconds and we didn't want to show that to the user.
The related
everest-operatorPR adds the 'creating' state to the DB CR. From the BE side there is nothing left to do except of updating theeverest-operatordependency to use the latest operator API, even though the DB statuses are not used in the codebase so far.Related PRs: