Skip to content

Commit

Permalink
mv: Do not error out when a bucket has an object lock config
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
Anis Elleuch committed Aug 10, 2023
1 parent 44ca181 commit 5ef7680
Showing 1 changed file with 0 additions and 12 deletions.
12 changes: 0 additions & 12 deletions cmd/mv-main.go
Original file line number Diff line number Diff line change
Expand Up @@ -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))

Expand Down

0 comments on commit 5ef7680

Please sign in to comment.