From 5ef76805df150acfe567d514d716b0218662b85a Mon Sep 17 00:00:00 2001 From: Anis Elleuch Date: Thu, 10 Aug 2023 15:47:51 +0100 Subject: [PATCH] mv: Do not error out when a bucket has an object lock config It appears that this code is coming from the old days when locking was implemented before versioning; It does not make sense now to make mv errors out when a bucket has a locking configuration. --- cmd/mv-main.go | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/cmd/mv-main.go b/cmd/mv-main.go index e14591949e..ca9b84cb0b 100644 --- a/cmd/mv-main.go +++ b/cmd/mv-main.go @@ -238,18 +238,6 @@ func mainMove(cliCtx *cli.Context) error { } } - // Check if source URLs does not have object locking enabled - // since we cannot move them (remove them from the source) - for _, urlStr := range cliCtx.Args()[:cliCtx.NArg()-1] { - enabled, err := isBucketLockEnabled(ctx, urlStr) - if err != nil { - fatalIf(err.Trace(), "Unable to get bucket lock configuration of `%s`", urlStr) - } - if enabled { - fatalIf(errDummy().Trace(), fmt.Sprintf("Object lock configuration is enabled on the specified bucket in alias %v.", urlStr)) - } - } - // Additional command speific theme customization. console.SetColor("Copy", color.New(color.FgGreen, color.Bold))