-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
S3: put_bucket_lifecyle
with multiple Transitions
#6388
Comments
put_bucket_lifecyle
vs put_bucket_lifecycle_configuration
Hi @ccatterina! We do already support I'm assuming that Line 1793 in 7b4cd49
Having multiple Transitions indeed fails against Moto, so if you want to create a fix (+ testcase) for this, that would be very welcome! Let us know if you need any help with this. |
Oh, ok. I didn't realize that! In that case it could also be helpful update the documentation, which now says that
Sure, I'll work on it in the coming weeks! I will open a PR as soon as I have something ready. |
put_bucket_lifecyle
vs put_bucket_lifecycle_configuration
put_bucket_lifecyle
with multiple Transitions
Handle multiple Transitions/NoncurrentVersionTranstions in bucket lifecycle configuration. Fixes getmoto#6388
Hi,
Moto implements the
put_bucket_lifecycle
API that should expect an array of AWS S3 Rule objects as input.From what I understand from looking at the code, moto implementation instead of parsing a
Rule
parse an object very similar to a AWS S3 Lifecycle Rule with the only exception that accept a singleTransition
instead of an array ofTransitions
.To fix this issue probably the best thing to do is to implement the
put_bucket_lifecycle_configuration
API, that expect an array ofLifecycle Rule
objects (like the current rules but with an array ofTransition
instead of a singleTransition
), and fix the currentput_bucket_lifecycle
API in order to make it to accept an Array ofRule
objects.What do you think about it?
if it's okay with you I could work on it and open a PR.
The text was updated successfully, but these errors were encountered: