Open MAXxATTAXx opened 4 years ago
Hi @MAXxATTAXx, thank you for creating this issue! while the AWS Go SDK / APIs do allow for more than 3 levels of nesting, unfortunately within the provider, we've come across #14062 in the web_acl resource by supporting essentially 1 root statement and 3 nested statements which creates a challenging practitioner experience. so at this time, development to support this feature is blocked but I'll update here if there are any changes that can enable this request in the near future.
Hi @anGie44, https://github.com/hashicorp/terraform-provider-aws/issues/14062 seems to be resolved now, is there anything else that is blocking development on this?
Hi @anGie44, just following up with a bit more details about this:
I hit the 3 level statement
nesting limitation while creating a rule group and tried to work around it by using lifecycle
and adding rule
to ignore_changes
, however even that does not work, terraform produces this error when running terraform plan
after adding more than 3 levels of nested statements via AWS console:
Error: Error setting rule: Invalid address to set: []string{"rule", "0", "statement", "0", "and_statement", "0", "statement", "1", "not_statement", "0", "statement", "0", "and_statement"}
At this point I'm planning to completely remove the offending rule group from terraform and manage it manually, but would love to hear about any workarounds or developments in this area.
With each extra rule costing $1, this lack of ability is starting to get expensive for us. Anything slightly complex can't be completed in a single rule. We would be perfectly happy for a deployment to take more time if it saved us having to split up everything into multiple smaller rules.
It's really not that hard to hit the limit of 3 nested statements, and it's incredibly upsetting that the limit is there, you essentially cripple a powerful AWS feature. I don't know what the provider does that even just 7 nested rules is slow, but unless it's literal hours I don't think it's worth removing the functionality altogether. Even 4 or 5 would be nice to have.
Hello
Do you have any news about this case ? It's vert penalizing...
Hello, news from this issue ?
Community Note
Description
Allow during provider definition on terraform code to set the max level of nested statement supported by the schema. Currently that value is hard coded to 3 max levels which excludes more complex use cases of the statement definition.
New or Affected Resource(s)
Potential Terraform Configuration
References