Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_data_lake_store add "Enable Firewall" option #1603

Closed
junbug178 opened this issue Jul 18, 2018 · 3 comments · Fixed by #1623
Closed

azurerm_data_lake_store add "Enable Firewall" option #1603

junbug178 opened this issue Jul 18, 2018 · 3 comments · Fixed by #1623

Comments

@junbug178
Copy link

Community Note

  • 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.

New or Affected Resource(s)

azurerm_data_lake_store
azurerm_data_lake_store_firewall_rule

Potential Terraform Configuration

References

@tombuildsstuff
Copy link
Contributor

appears there's a FirewallState which can be set at the Data Lake Store level which can be used to set this

@tombuildsstuff
Copy link
Contributor

I'm bundling this up with #1623

@tombuildsstuff tombuildsstuff changed the title azurerm_data_lake_store_firewall_rule add "Enable Firewall" option azurerm_data_lake_store add "Enable Firewall" option Jul 21, 2018
@tombuildsstuff tombuildsstuff modified the milestones: 1.10.0, 1.11.0 Jul 21, 2018
@ghost
Copy link

ghost commented Mar 30, 2020

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 ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants