-
Notifications
You must be signed in to change notification settings - Fork 398
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
efs - Add support to specify the number of days to transition to inactive storage #522
efs - Add support to specify the number of days to transition to inactive storage #522
Conversation
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.
Thanks for taking the time to raise this PR.
Change generally looks sound. Some minor formatting issues picked up by the linter.
In addition please add a changelog https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
Last time I looked the EFS integration tests were broken so it may take a while before I would be able to fully validate this change as I'm not actively using EFS at this time.
46b066c
to
db8ed0c
Compare
Depends on mattclay/aws-terminator#177 |
recheck |
recheck |
b138f51
to
b061ee6
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!
Refactor ec2_eni tagging code SUMMARY Use the shared ec2 tagging code for tagging ENIs. Also fixes the test instability (caused by a race condition with VM states) ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_eni ADDITIONAL INFORMATION Reviewed-by: Felix Fontein <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
SUMMARY
Support setting EFS lifecycle policy.
ISSUE TYPE
COMPONENT NAME
community.aws.efs
ADDITIONAL INFORMATION
This is now possible: