-
Notifications
You must be signed in to change notification settings - Fork 632
feat: support multiple public ips in connectivity firewall #1243
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
base: main
Are you sure you want to change the base?
feat: support multiple public ips in connectivity firewall #1243
Conversation
index b666ac8..49bcf28 100644
--- a/02-connectivity/main.tf
+++ b/02-connectivity/main.tf
@@ -13,8 +13,7 @@ resource "azurerm_virtual_wan" "vwan" {
module "connectivity" {
- source = "Azure/caf-enterprise-scale/azurerm"
- version = "6.2.1"
+ source = "github.com/tobiasehlert/terraform-azurerm-caf-enterprise-scale.git?ref=feat-multiple-public-ips-in-hub-firewall"
# Disable telemetry
disable_telemetry = true
diff --git a/02-connectivity/settings.nwe.vwan.connectivity.tf b/02-connectivity/settings.nwe.vwan.connectivity.tf
index fe655a1..28db3f5 100644
--- a/02-connectivity/settings.nwe.vwan.connectivity.tf
+++ b/02-connectivity/settings.nwe.vwan.connectivity.tf
@@ -39,6 +39,7 @@ locals {
azure_firewall = {
enabled = true
config = {
+ public_ip_count = 8
enable_dns_proxy = true
dns_servers = [azurerm_private_dns_resolver_inbound_endpoint.dns_hub_ext_vnet_nwe.ip_configurations[0].private_ip_address]
sku_tier = "Premium" After making these changes in my Terraform configuration, I only get changes to outputs. Am I missing something obvious?
|
@magnus-longva-bouvet, oh yeah.. I only added that for |
Can maybe @matt-FFFFFF review this PR? |
/azp run unit |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Pull Request Overview
This PR adds support for deploying multiple public IPs for the connectivity firewall, allowing users to specify the number of public IPs via the new parameter "public_ip_count".
- Added "public_ip_count" to the root README.md.
- Added "public_ip_count" to the modules/connectivity/README.md.
Reviewed Changes
Copilot reviewed 2 out of 5 changed files in this pull request and generated no comments.
File | Description |
---|---|
README.md | Documentation update to include the public_ip_count parameter |
modules/connectivity/README.md | Documentation update to include the public_ip_count parameter |
Files not reviewed (3)
- modules/connectivity/locals.tf: Language not supported
- modules/connectivity/variables.tf: Language not supported
- variables.tf: Language not supported
@matt-FFFFFF, is there something that I can do in terms of this PR? |
Is this PR stalled somehow? We really need this. Is there anything we can do to help move this along? |
Overview/Summary
This PR gives the possibility to the connectivity module the option to specify how many public IPs you want to have deployed as part of your landing zone.
The default is set to be one, but when specifying more, you get multiple IPs provisioned and associated with the firewall in the hub_network.
The naming of azurerm_public_ip resource are -pip, -pip-2, pip-3 and so on, so nothing gets removed.
This PR fixes/adds/changes/removes
Breaking Changes
None.
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