Open digitalfiz opened 6 years ago
Is there any update on this? We have a similar requirement and looking for a workaround.
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
I think these bot actions that mark issues as stale are the reason why so many issues have people just commenting +1 on them. Inaction on the devs part does not signify a problem has just magically gone away.
I know this is an old issue, but I'd like to add a +1 here. There is a pretty big use case for this: ACLs created by the FIrewall Manager that need to have additional rules added at a more granular level. The only way to handle this atm is to import the resources into the TF state after the Firewall Manager has created them, which is quite tedious.
Adding a +1 here. The workflow for importing this into terraform and working with it is quite annoying, and even when imported, it makes it very difficult to add rules in a maintainable or repeatable way across multiple deployments.
Description
Add a
aws_waf_rule_attach
resource so rules can be attached to groups or ACL's directly later. Kind of like how security groups work. Where you can choose to add ingress or egress rules directly in the sg resource or attach them later.New or Affected Resource(s)
Potential Terraform Configuration
References
none that I could find