-
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
r/s3_bucket_lifecycle_configuration: correctly configure filter
tag
and add and
block documentation
#23252
r/s3_bucket_lifecycle_configuration: correctly configure filter
tag
and add and
block documentation
#23252
Conversation
and
block config detailsfilter
tag and add
and` block documentation
filter
tag and add
and` block documentationfilter
tag
and add and
block documentation
26c561f
to
b431de6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MPB 🎉
% make testacc TESTS=TestAccS3BucketLifecycle PKG=s3 ACCTEST_PARALLELISM=5
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 5 -run='TestAccS3BucketLifecycle' -timeout 180m
--- PASS: TestAccS3BucketLifecycleConfiguration_basic (198.58s)
--- PASS: TestAccS3BucketLifecycleConfiguration_TransitionZeroDays_intelligentTiering (198.96s)
--- PASS: TestAccS3BucketLifecycleConfiguration_TransitionStorageClassOnly_intelligentTiering (199.20s)
--- PASS: TestAccS3BucketLifecycleConfiguration_RuleExpiration_expireMarkerOnly (279.70s)
--- PASS: TestAccS3BucketLifecycleConfiguration_TransitionUpdateBetweenDaysAndDate_intelligentTiering (335.33s)
--- PASS: TestAccS3BucketLifecycleConfiguration_TransitionDate_standardIa (195.21s)
--- PASS: TestAccS3BucketLifecycleConfiguration_TransitionDate_intelligentTiering (195.65s)
--- PASS: TestAccS3BucketLifecycleConfiguration_RuleExpiration_emptyBlock (194.92s)
--- PASS: TestAccS3BucketLifecycleConfiguration_ruleAbortIncompleteMultipartUpload (275.88s)
--- PASS: TestAccS3BucketLifecycleConfiguration_disappears (54.79s)
--- PASS: TestAccS3BucketLifecycleConfiguration_multipleRules (195.78s)
--- PASS: TestAccS3BucketLifecycleConfiguration_prefix (192.20s)
--- PASS: TestAccS3BucketLifecycleConfiguration_filterWithPrefix (276.06s)
--- PASS: TestAccS3BucketLifecycleConfiguration_disableRule (340.00s)
--- PASS: TestAccS3BucketLifecycleConfiguration_Filter_Tag (203.28s)
--- PASS: TestAccS3BucketLifecycleConfiguration_nonCurrentVersionTransition (191.94s)
--- PASS: TestAccS3BucketLifecycleConfiguration_nonCurrentVersionExpiration (192.04s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/s3 861.198s
@@ -208,6 +190,15 @@ The `transition` configuration block supports the following arguments: | |||
* `days` - (Optional, Conflicts with `date`) The number of days after creation when objects are transitioned to the specified storage class. The value must be a positive integer. If both `days` and `date` are not specified, defaults to `0`. Valid values depend on `storage_class`, see [Transition objects using Amazon S3 Lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html) for more details. | |||
* `storage_class` - The class of storage used to store the object. Valid Values: `GLACIER`, `STANDARD_IA`, `ONEZONE_IA`, `INTELLIGENT_TIERING`, `DEEP_ARCHIVE`, `GLACIER_IR`. | |||
|
|||
### and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the upgrade guide having filter
examples using and
and just prefix
.
This functionality has been released in v4.2.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! |
The bug reported in #23132 was for version 4.0.0, was fixed in 4.1.0 and is now a problem again in 4.2.0, likely due to the change in this PR. Could the bug be reopened again, please? |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #23239
Output from acceptance testing: