New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no 'replicate status' without replication config #15233
Merged
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
'replicate status' shouldn't be displaying historic values unless replication config is present on the relevant bucket.
harshavardhana
force-pushed
the
reject-metrics
branch
from
July 6, 2022 07:55
e1d96d2
to
a5c0a9b
Compare
Mint Automation
15233-a5c0a9b/mint-pools.sh.log:
15233-a5c0a9b/mint-large-bucket.sh.log:
15233-a5c0a9b/mint-erasure.sh.log:
Deleting image on docker hub |
krisis
approved these changes
Jul 6, 2022
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.
Description
no 'replicate status' without replication config
Motivation and Context
'replicate status' shouldn't be displaying historic
values unless replication config is present on the
relevant bucket.
How to test this PR?
'mc replicate rm' a previous config and attempt
'mc replicate status' with or without this PR.
Types of changes
Checklist:
commit-id
orPR #
here)