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
Add optional action setting for "Allow" or "Deny" to the service_config -> ip_restriction block.
The changes made by Pull Request #6705 doesn't permit the ability to set if this is an Allow or Deny rule. When this is applied the rules are always made to be allow, and default deny rule is added. Any exiting rules are deleted.
In the event that some IPs may need to be blocked in the provided IP range / VNET, an ARM template must still be used to setup those deny rules.
New or Affected Resource(s)
azurerm_app_service
Potential Terraform Configuration
ip_restriction= [
{
ip_address ="1.2.3.0/24"# This exists today
name ="foo"# This exists today
priority =101# This exists today
},
{
ip_address ="1.2.3.4/32"# This exists today
name ="bar"# This exists today
priority =100# This exists today
action ="Deny"
}
]
The text was updated successfully, but these errors were encountered:
jjperry69
changed the title
Support for Allow or Deny in ip_restriction of azurerm_app_service
Support for Action of Allow or Deny in ip_restriction of azurerm_app_service
May 13, 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!
Community Note
Description
Add optional action setting for "Allow" or "Deny" to the service_config -> ip_restriction block.
The changes made by Pull Request #6705 doesn't permit the ability to set if this is an Allow or Deny rule. When this is applied the rules are always made to be allow, and default deny rule is added. Any exiting rules are deleted.
In the event that some IPs may need to be blocked in the provided IP range / VNET, an ARM template must still be used to setup those deny rules.
New or Affected Resource(s)
Potential Terraform Configuration
References
azurerm_app_service
ip_restriction
- support forname
&priority
#6705 Support for name and priority in ip_restriction of azurerm_app_service #6388The text was updated successfully, but these errors were encountered: