-
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
fix: Set max # of lifecycle_policy blocks to 3 to allow setting all policies #35522
fix: Set max # of lifecycle_policy blocks to 3 to allow setting all policies #35522
Conversation
Community NoteVoting for Prioritization
For Submitters
|
1ca799c
to
dc2da95
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.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccEFSFileSystem_lifecyclePolicy' PKG=efs
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/efs/... -v -count 1 -parallel 20 -run=TestAccEFSFileSystem_lifecyclePolicy -timeout 360m
=== RUN TestAccEFSFileSystem_lifecyclePolicy
=== PAUSE TestAccEFSFileSystem_lifecyclePolicy
=== CONT TestAccEFSFileSystem_lifecyclePolicy
--- PASS: TestAccEFSFileSystem_lifecyclePolicy (121.65s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/efs 145.656s
@acwwat Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.35.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 pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This PR is to fix the maximum number of
lifecycle_policy
config blocks to allow all 3 supported types of policies in theaws_efs_file_system
resource. While working on the fix, I noticed that the resource doc was a bit outdated, so I have adjusted the formatting and the valid values.I also noticed that file system protection now supports a "REPLICATING" value, but the code seems to be written in a way to exclude that value. I am not sure if that was the intention, so I will open a new issue later to track the investigation. For now let's stick to fixing lifecycle policy in this PR.
Relations
Closes #35314
References
Referred to LifecyclePolicy API data type reference for supported values.
Output from Acceptance Testing