History

reject resync start on misconfigured replication rules (#15041)

we expect resync to start on buckets with replication rule ExistingObjects enabled, if not we reject such calls.

Harshavardhana committed 4 years ago

Commit 48e367f1 parent fd024928 files · +519 −383Browse files

Showing the changes to cmd/api-errors.go (1 of 8 files). Show all

Unified · Split

cmd/api-errors.go+4−4
@@ -131,7 +131,7 @@ const ( · 130 unmodified lines
131131 ErrReplicationNeedsVersioningError
132132 ErrReplicationBucketNeedsVersioningError
133133 ErrReplicationDenyEditError
134− ErrReplicationNoMatchingRuleError
134+ ErrReplicationNoExistingObjects
135135 ErrObjectRestoreAlreadyInProgress
136136 ErrNoSuchKey
137137 ErrNoSuchUpload
@@ -893,9 +893,9 @@ var errorCodes = errorCodeMap{ · 755 unmodified lines
893893 Description: "Bandwidth limit for remote target must be atleast 100MBps",
894894 HTTPStatusCode: http.StatusBadRequest,
895895 },
896− ErrReplicationNoMatchingRuleError: {
897− Code: "XMinioReplicationNoMatchingRule",
898− Description: "No matching replication rule found for this object prefix",
896+ ErrReplicationNoExistingObjects: {
897+ Code: "XMinioReplicationNoExistingObjects",
898+ Description: "No matching ExistingsObjects rule enabled",
899899 HTTPStatusCode: http.StatusBadRequest,
900900 },
901901 ErrReplicationDenyEditError: {

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t