You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aws_s3_bucket_lifecycle_configuration.default[0]: Modifying... [id=xxx]
╷
│ Error: updating S3 Bucket (xxx) Lifecycle Configuration
│
│ with aws_s3_bucket_lifecycle_configuration.default[0],
│ on lifecycle.tf line 159, in resource "aws_s3_bucket_lifecycle_configuration" "default":
│ 159: resource "aws_s3_bucket_lifecycle_configuration" "default" {
│
│ operation error S3: PutBucketLifecycleConfiguration, https response error
│ StatusCode: 400, RequestID: XXX, HostID:
│ XXX,
│ api error MalformedXML: The XML you provided was not well-formed or did not
│ validate against our published schema
╵
ERRO[0019] terraform invocation failed in /home/XXX/.terragrunt-cache/xxx
ERRO[0019] error occurred:
* Failed to execute "terraform apply" in /home/xxx/.terragrunt-cache/xxx
╷
│ Error: updating S3 Bucket (xxx) Lifecycle Configuration
│
│ with aws_s3_bucket_lifecycle_configuration.default[0],
│ on lifecycle.tf line 159, in resource "aws_s3_bucket_lifecycle_configuration" "default":
│ 159: resource "aws_s3_bucket_lifecycle_configuration" "default" {
│
│ operation error S3: PutBucketLifecycleConfiguration, https response error
│ StatusCode: 400, RequestID:xxx, HostID:
│ XXX,
│ api error MalformedXML: The XML you provided was not well-formed or did not
│ validate against our published schema
╵
exit status 1
I can add that if I not specify filter at all, it not even trying to remove existing minimun object size
Expected Behavior
Update the mimimum object size object
Steps to Reproduce
Create bucket using that module and that example config
Describe the Bug
I am using cloudposse s3-bucket 4.10.0 version. I have set terragrunt object with following schema
When I remove the object_size_greater_than it works fine.
Following terraform output:
The error:
I can add that if I not specify filter at all, it not even trying to remove existing minimun object size
Expected Behavior
Update the mimimum object size object
Steps to Reproduce
Create bucket using that module and that example config
lifecycle_configuration_rules=[
{
enabled = true
id = "deletion_archive"
expiration = {
days = 30
}
noncurrent_version_expiration = {
noncurrent_days = 30
}
filter_and = {
object_size_greater_than = 1
prefix = "xxx/archive/"
}
}
]
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: