-
Notifications
You must be signed in to change notification settings - Fork 578
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
Add Firewall Policy #331
Merged
Merged
Add Firewall Policy #331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…erm-caf-enterprise-scale into add-fw-policy
matt-FFFFFF
reviewed
Apr 8, 2022
Also fix issue introduced by replacing `try()` with `lookup()`
/azp run unit |
Azure Pipelines successfully started running 1 pipeline(s). |
matt-FFFFFF
approved these changes
Apr 14, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Apr 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview/Summary
This PR adds an
azurerm_firewall_policy
resource for eachazurerm_firewall
created by the module.To enable DNS proxy settings, each Azure Firewall needs to be associated with an Azure Firewall Policy. The Azure Firewall Policy also enables other firewall settings to be configured, including:
base_policy_id
private_ip_ranges
sku
(should match the firewall sku)threat_intelligence_mode
threat_intelligence_allowlist
identity
insights
intrusion_detection
This PR fixes/adds/changes/removes
azurerm_firewall_policy
resource for eachazurerm_firewall
created by the moduleenable_dns_proxy
feature flag for Azure Firewall settings (enabled via the attached Firewall Policy), including the ability to set customdns_servers
debug
output for theconnectivity
child module to ensure alllocals
are includedazurerm_public_ip
resource types (previously missing) as discussed in How can I rename resources? #332Breaking Changes
configure_connectivity_resources.settings.hub_networks[*].config.azure_firewall.config
input object to enable configuration of common settings for the newazurerm_firewall_policy
resources:dns_servers
base_policy_id
private_ip_ranges
threat_intelligence_mode
threat_intelligence_allowlist
name
field was being addressed by a differentscope
than the other properties. To improve consistency and flatten thescope
object, we have updated the following resources:name
field forazurerm_virtual_network_gateway["expressroute"]
has been updated toazurerm_virtual_network_gateway["connectivity_expressroute"]
azurerm_virtual_network_gateway["connectivity"]["ergw"]
have been updated toazurerm_virtual_network_gateway["connectivity_expressroute"]
azurerm_public_ip["connectivity"]["ergw"]
have been updated toazurerm_public_ip["connectivity_expressroute"]
name
field forazurerm_virtual_network_gateway["vpngw"]
has been updated toazurerm_virtual_network_gateway["connectivity_vpn"]
azurerm_virtual_network_gateway["connectivity"]["vpngw"]
have been updated toazurerm_virtual_network_gateway["connectivity_vpn"]
azurerm_public_ip["connectivity"]["vpn"]
have been updated toazurerm_public_ip["connectivity_vpn"]
azurerm_public_ip["connectivity"]["azfw"]
have been updated toazurerm_public_ip["connectivity_firewall"]
The following is an example showing the required
config
object forazure_firewall
settings:The following is an example advanced config object reflecting some of these changes:
Testing Evidence
Please provide any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
As part of this Pull Request I have
main
branch/docs/wiki/whats-new.md
)