Describe the solution you'd like
The cache bucket lifecycle rules don't allow for deletion of noncurrent cache objects. The terraform resource does not allow for extension (multiple lifecycle attachments) and attempts to override result in flip-flop persistent diffs.
One or both of the following is suggested:
- allow disabling creation of the lifecycle policy, so a custom lifecycle can be attached
- add a variable
noncurrent_retention_days and a noncurrent deletion action rule
Describe alternatives you've considered
I have tried overriding with custom policy, but end up with two competing resources.
I have considered creating my own bucket resource and not using the cache module, which I might do now - I should be able to just use moved blocks to handle the state migration.
Describe the solution you'd like
The cache bucket lifecycle rules don't allow for deletion of noncurrent cache objects. The terraform resource does not allow for extension (multiple lifecycle attachments) and attempts to override result in flip-flop persistent diffs.
One or both of the following is suggested:
noncurrent_retention_daysand a noncurrent deletion action ruleDescribe alternatives you've considered
I have tried overriding with custom policy, but end up with two competing resources.
I have considered creating my own bucket resource and not using the cache module, which I might do now - I should be able to just use moved blocks to handle the state migration.