[go: up one dir, main page]

Skip to content
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

PutBucketLifecycle(deprecated) vs PutBucketLifecycleConfiguration #20632

Open
vlvicente opened this issue Nov 11, 2024 Discussed in #20580 · 0 comments
Open

PutBucketLifecycle(deprecated) vs PutBucketLifecycleConfiguration #20632

vlvicente opened this issue Nov 11, 2024 Discussed in #20580 · 0 comments
Assignees

Comments

@vlvicente
Copy link

Discussed in #20580

Originally posted by vlvicente October 23, 2024
Can anyone confirm that the new version of LifecycleConfiguration is not yet supported by MinIO?
Context: I've been trying to programmatically add a lifecycle configuration to a bucket, which is rejected with a bad request saying the XML is not wellformed. I'm using rust-s3 which only implements the new version and the xml does seem well formed and within the specs defined by AWS.
Taking a look at the MinIO implementation I noticed that one of the validations made is this one:

func (r Rule) validatePrefixAndFilter() error {
 if !r.Prefix.set && r.Filter.IsEmpty() || r.Prefix.set && !r.Filter.IsEmpty() {
   return errXMLNotWellFormed
 }
 if !r.Prefix.set {
   return r.Filter.Validate()
 }
 return nil
}

which seems to consider the deprecated version of the request (in which the Prefix field is in the same level as Filter and marked as required) instead of new version (Prefix is moved inside the Filter field)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants