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
We should enhance the azurerm_network_security_rule resource to support setting these fields, from what I can see these are exposed as the ID's in the API (rather than the name's) - and exist in the Go SDK (v12 / 2017-09-01)
The text was updated successfully, but these errors were encountered:
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
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As documented in this blog post - it's possible to attach NSG Rules to an Application Security Group by specifying the Source/Destination ASG:
We should enhance the
azurerm_network_security_rule
resource to support setting these fields, from what I can see these are exposed as the ID's in the API (rather than the name's) - and exist in the Go SDK (v12 /2017-09-01
)The text was updated successfully, but these errors were encountered: