Add support for augmented security rules. #692
Conversation
|
Great ! This feature will make more readable our set or Security Rules. |
|
I've run the Network Security Group/Rule tests and all the tests pass:
|
|
|
||
| * `destination_address_prefix` - (Optional) CIDR or destination IP range or * to match any IP. Tags such as ‘VirtualNetwork’, ‘AzureLoadBalancer’ and ‘Internet’ can also be used. This is required if `destination_address_prefixes` is not specified. | ||
|
|
||
| * `destination_address_prefixes` - (Optional) List of destination address prefixes. Tags may not be used. This is required if `destination_address_prefix` is not specified. |
There was a problem hiding this comment.
we may in future want to add some validation for these rules (i.e. that either destination_address_prefix or destination_address_prefixes is set in the Create/Update method) - but this should suffice for now
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
Resolves #659. Allows creating augmented network security rules.
https://docs.microsoft.com/en-us/azure/virtual-network/security-overview#augmented-security-rules