Add option to force drop database before restore #1639
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
TheRealHaoLiu
changed the title
rooftopcellist
approved these changes
Nov 15, 2023
|
Looks great, let's merge it? |
|
@rooftopcellist mention he's gonna actually test it 🤣 instead of just rubber stamping my PR |
dsavineau
reviewed
Nov 27, 2023
Co-authored-by: Dimitri Savineau <[email protected]>
This was referenced Dec 5, 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.
SUMMARY
Based on #1604
Help with recovery from a bad restore or any other database "accident" where the database is left in a state that can't perform "clean" during restore process properly
Added
force_drop_dboption in AWXRestoreISSUE TYPE
ADDITIONAL INFORMATION
Fixes #1587