Open steveharanexperian opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
I want multiple rules, but it doesn't seem to like it
Hi @steveharanexperian, could you look at this workaround https://github.com/hashicorp/terraform-provider-aws/issues/14094#issuecomment-655625254. I had tried it , and it works
Was having the same problem and used the workaround linked. Fixed the problem. Essentially you have to add an override_action block to each managed rule group block.
This bug applies to 'rule_group_reference_statement' as well
So, couldn't terraform-provider-aws check that for us, and flag a problem when there's neither an override_action
nor a action
defined? Or, maybe, compute a sane default of override_action { none {} }
?
Terraform Core Version
1.1.7
AWS Provider Version
latest
Affected Resource(s)
For this TF:
Expected Behavior
The plan and apply should work
Actual Behavior
The plan works, but the apply throws:
Error reason: You have used none or multiple values for a field that requires exactly one value., field: RULE, parameter: Rule", Parameter: "Rule", Reason: "You have used none or multiple values for a field that requires exactly one value.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
.
Debug Output
Error reason: You have used none or multiple values for a field that requires exactly one value., field: RULE, parameter: Rule", Parameter: "Rule", Reason: "You have used none or multiple values for a field that requires exactly one value.
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None