-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: aws_s3_bucket_lifecycle_configuration with filter object_size_greater_than = "0" doesn't work #28851
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Looking at the documentation, it has to be specified as an int but even, it's not working. |
Hi, |
Anybody having same issue? |
I have tested the fix proposed by @pvbouwel. It works actually and solve my issue. |
This functionality has been released in v4.62.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.3.7
AWS Provider Version
4.49.0
Affected Resource(s)
aws_s3_bucket_lifecycle_configuration
=> filter object_size_greater_than
Expected Behavior
object_size_greater_than = "0"
Terraform apply completes successfully and changes in the AWS console visible.
A reapply doesn't show any change.
Actual Behavior
object_size_greater_than = "0"
Terraform apply completes successfully but no change in the AWS console visible.
A reapply shows the same change as not executed in AWS.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
object_size_greater_than = "0" in filter of lifecycle configuration rule.
Terraform apply completes successfully but no change in the AWS console visible.
A reapply shows the same change as not executed in AWS.
No object_size_greater_than in the API call :
<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Rule><Filter><Prefix></Prefix></Filter><ID>Lifecycle</ID><NoncurrentVersionExpiration><NoncurrentDays>14</NoncurrentDays></NoncurrentVersionExpiration><Status>Enabled</Status><Expiration><Days>14</Days></Expiration></Rule></LifecycleConfiguration>
object_size_greater_than = "1"
Terraform apply completes successfully and change in the AWS console visible.
A reapply doesn't show any change.
object_size_greater_than in API call :
<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Rule><Expiration><Days>14</Days></Expiration><Filter><ObjectSizeGreaterThan>1</ObjectSizeGreaterThan></Filter><ID>Lifecycle</ID><NoncurrentVersionExpiration><NoncurrentDays>14</NoncurrentDays></NoncurrentVersionExpiration><Status>Enabled</Status></Rule></LifecycleConfiguration>
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: