You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Description
It should also be possible to assign a DDOS Protection Plan to a VNET in a separate resource. This is useful if the VNET is not created in the respective root, but is referenced via a data object.
Name for this resource could be azurerm_network_ddos_protection_plan_association or azurerm_virtual_network_ddos_protection_plan_association.
Is there an existing issue for this?
Community Note
Description
It should also be possible to assign a DDOS Protection Plan to a VNET in a separate resource. This is useful if the VNET is not created in the respective root, but is referenced via a data object.
Name for this resource could be azurerm_network_ddos_protection_plan_association or azurerm_virtual_network_ddos_protection_plan_association.
New or Affected Resource(s)/Data Source(s)
azurerm_network_ddos_protection_plan_association
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: