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 "+1" or "me too" comments, 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
Description
Although we can create the ip rules to add to the firewall, there is not an option to enable firewall. Thus, adding ip addresses to the firewall does virtually nothing as the firewall is "off".
This is my first time submitting a request so I apologize in advance if I didn't get all of the information required.
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 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
Although we can create the ip rules to add to the firewall, there is not an option to enable firewall. Thus, adding ip addresses to the firewall does virtually nothing as the firewall is "off".
This is my first time submitting a request so I apologize in advance if I didn't get all of the information required.
New or Affected Resource(s)
azurerm_data_lake_store
azurerm_data_lake_store_firewall_rule
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: