Add support for blue/green deployment in mongodb role #273
Conversation
This file contains hidden or 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
steven-schattenberg-itential
requested review from
Amunagala-itential,
Madias2222,
Nick-Andreano,
bill-minear and
kvelarde-itential
Contributor
|
Can you update the name of the PR - something like "Add support for blue/green deployment in mongodb role" maybe? |
steven-schattenberg-itential
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changed MongoDB role to check before each mongo feature is enabled the current state of the mongo server. Depending on the results tasks are now skipped or not depending on the state of the server. For example, if authorization is already enabled then those tasks will be skipped which will prevent taking steps backward.