Move from count to for_each for azurerm_network_security_rule
juanjojulian opened this issue · 0 comments
juanjojulian commented
Is there an existing issue for this?
- I have searched the existing issues
Description
Hi, and thanks for the effort to develop and maintain this module.
Is there any plan to move from 'count' iterations to 'for_each' in azurerm_network_security_rule resource creation?.
Right now, and because of how 'count' works, if I remove a single rule every rule created after it has to be 'replaced' (destroy/add), that may work for NSG's with a small set of rules, but for large sets could be a problem. Using for_each instead of count would solve this problem. I can help if needed.
New or Affected Resource(s)/Data Source(s)
azurerm_network_security_rule
Potential Terraform Configuration
No response
References
No response