Introduce object storage cleaning on the shard scope (by default) #229
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
Alex-Burmak
approved these changes
Aug 23, 2024
| is_flag=True, | ||
| help=("List objects on all hosts in a cluster."), | ||
| help=("List objects on all hosts in a cluster. Deprecated, see --clean-scope"), |
There was a problem hiding this comment.
I'd just drop it without deprecation :)
There was a problem hiding this comment.
I don't mind, done it
aalexfvk
deleted the
MDB-30597_Introduce_s3_cleaning_on_the_shard_scope
branch
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.
remote/remoteSecuretable functions.--clean-scopeforobject-storage cleancommand with possible valueshost,shard,cluster.shardis used by default.--on-clusterparameter. Now it is not respected anymore. Add hint about this in the help message.