-
-
Notifications
You must be signed in to change notification settings - Fork 839
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
Lifcycle Rules enforce mutually exclusive defaults #87
Comments
I've had a look at this to see if I could get a work round. It looks like this is something that is going to be addressed when the defaults funciton is finally added https://www.terraform.io/docs/language/functions/defaults.html In the meantime, the only way I could get this to work at all, was to remove the default list and replace it with
Happy to sort out a PR for the above if there isn't some other trick that can be done with dynamic blocks that I'm not aware of. |
Yes, were waiting on the ability to make keys optional. We want the default lifecycle list. You could override the default by setting an empty list for that input variable when calling the module. |
Hi, any ideas when this issue will be resolved? |
Have you tried this? |
Describe the Bug
The lifecycle rule blocks intoduced in 0.35.0 enforces mutually exclusive defaults when enabled.
When enabled each of the options need to be declared when calling the module.
When you run with a fully declared lifecycle_rules your get this error
If you remove the tags option you get:
If you leave tags and remove abort_incomplete_multipart_upload_days:
Expected Behavior
I should only need to do:
rather than
Steps to Reproduce
Steps to reproduce the behavior:
Define a lifecycle rule as per the long example given above. You will get an error advising tags and abort_incomplete_multipart_upload_days can not both be defined. Adress that error either way and try and run again. You will get an error saying each element is required.
Environment (please complete the following information):
Terraform v0.15.3
on darwin_amd64
The text was updated successfully, but these errors were encountered: