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_firewall_policy_rule_collection_group does not support web categories #12944

Closed
PlanetWilson opened this issue Aug 11, 2021 · 2 comments · Fixed by #13190
Closed

azurerm_firewall_policy_rule_collection_group does not support web categories #12944

PlanetWilson opened this issue Aug 11, 2021 · 2 comments · Fixed by #13190

Comments

@PlanetWilson
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

Azure firewalls now support a web category rule which allows URL filtering based on a number of categories like Gambling, File sharing etc. There is no way to define these in a azurerm_firewall_policy_rule_collection_group right now which means I can't manage my firewall

New or Affected Resource(s)

  • azurerm_firewall_policy_rule_collection_group

Potential Terraform Configuration

rule {
      name = "Internet_Access"
      
      web_categories = ["category 1", "category 2"]

      source_addresses = [
        "10.51.0.0/20",
      ]
      source_ip_groups = []

      protocols {
        port = 443
        type = "Https"
      }
      protocols {
        port = 80
        type = "Http"
      }
    } 
@github-actions
Copy link

This functionality has been released in v2.76.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.