History

fix: object lock behavior when default lock config is enabled (#9305)

kannappanr committed 6 years ago

Commit 1fa65c71 parent cc9b63e6 files · +38 −13Browse files

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

Unified · Split

cmd/api-errors.go+7−1
@@ -151,6 +151,7 @@ const ( · 150 unmodified lines
151151 ErrBadRequest
152152 ErrKeyTooLongError
153153 ErrInvalidBucketObjectLockConfiguration
154+ ErrObjectLockConfigurationNotFound
154155 ErrObjectLockConfigurationNotAllowed
155156 ErrNoSuchObjectLockConfiguration
156157 ErrObjectLocked
@@ -765,9 +766,14 @@ var errorCodes = errorCodeMap{ · 608 unmodified lines
765766 Description: "Bucket is missing ObjectLockConfiguration",
766767 HTTPStatusCode: http.StatusBadRequest,
767768 },
769+ ErrObjectLockConfigurationNotFound: {
770+ Code: "ObjectLockConfigurationNotFoundError",
771+ Description: "Object Lock configuration does not exist for this bucket",
772+ HTTPStatusCode: http.StatusNotFound,
773+ },
768774 ErrObjectLockConfigurationNotAllowed: {
769775 Code: "InvalidBucketState",
770− Description: "Object Lock configuration cannot be enabled on existing buckets.",
776+ Description: "Object Lock configuration cannot be enabled on existing buckets",
771777 HTTPStatusCode: http.StatusConflict,
772778 },
773779 ErrNoSuchObjectLockConfiguration: {

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