Lifecycle rule defined in backup rule should be used when not explicitly defined in _copyaction ("Use the same settings from backup rule").
Actual Behavior
When _copyaction is used without lifecycle definition, in AWS console you can see that "Custom lifeycle" is chosen and "Total retention period" settings are empty in the "Copy to destination - optional)" section and "Total retention (years)" is at "10+" which could result in high backup storage cost if not noticed.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.8.5
AWS Provider Version
5.52.0
Affected Resource(s)
Expected Behavior
Lifecycle rule defined in backup rule should be used when not explicitly defined in _copyaction ("Use the same settings from backup rule").
Actual Behavior
When _copyaction is used without lifecycle definition, in AWS console you can see that "Custom lifeycle" is chosen and "Total retention period" settings are empty in the "Copy to destination - optional)" section and "Total retention (years)" is at "10+" which could result in high backup storage cost if not noticed.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None