drop rgw multisite deployment support #7474
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
The current approach is extremely complex and introduced a lot of spaghetti code. This doesn't offer a good user experience at all. It's time to think to another approach (dedicated playbook) and drop the current implementation in order to clean up the code. Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
guits
force-pushed
the
drop-rgw-multisite
branch
14 times, most recently
from
93a3c86 to
3704509
Compare
guits
changed the title
guits
force-pushed
the
drop-rgw-multisite
branch
3 times, most recently
from
b52941f to
39675d2
Compare
This addresses all errors reported by the Ansible linter. Signed-off-by: Guillaume Abrioux <gabrioux@ibm.com>
guits
force-pushed
the
drop-rgw-multisite
branch
from
39675d2 to
89ae014
Compare
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.
The current approach is extremely complex and introduced a lot of spaghetti code. This doesn't offer a good user experience at all.
It's time to think to another approach (dedicated playbook) and drop the current implementation in order to clean up the code.