Skip to content

feat: support multiple public ips on firewall #135

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

Conversation

tobiasehlert
Copy link
Contributor

@tobiasehlert tobiasehlert commented Jun 11, 2025

Description

This pull request adds support to have multiple public ips on firewall resource.

Similar implementation as in Azure/terraform-azurerm-caf-enterprise-scale#1243.

Fixes #76

Type of Change

  • Non-module change (e.g. CI/CD, documentation, etc.)
  • Azure Verified Module updates:
    • Bugfix containing backwards compatible bug fixes
      • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
      • The bug was found by the module author, and no one has opened an issue to report it yet.
    • Feature update backwards compatible feature updates.
    • Breaking changes.
    • Update to documentation

Checklist

  • I'm sure there are no other open Pull Requests for the same update/change
  • My corresponding pipelines / checks run clean and green without any errors or warnings
  • I did run all pre-commit checks

@tobiasehlert tobiasehlert force-pushed the feat-support-multiple-public-ips-on-firewall branch from f516071 to 4274009 Compare June 12, 2025 19:34
Copy link
Member

@jaredfholgate jaredfholgate left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi. I very much appreciate you submitting this PR. I'm just wondering if we can make the implementation a bit cleaner and more scalable for new features moving forward. Thanks

@tobiasehlert tobiasehlert requested a review from a team as a code owner June 24, 2025 07:23
@tobiasehlert
Copy link
Contributor Author

Hi @jaredfholgate, I've rewritten the logic so that you'd need to specify a map now instead.
In the basic-example you can see, how the whole configuration would look like, since I added a secondary IP there.

One outstanding issue is the moved-block you asked me to look into. From what I can see it's not possible to specify such a think since there is a lack of doing those dynamically. If Terraform would have the option to make the moved-block to be generated by some key/value kind of way, that would be doable, but it isn't.

The end-user of this module would need to specify it's own moved block so that the pip is not recreated. Which was also the reason why I tried to make it non-breaking but made the code much more harder to read.

@jaredfholgate
Copy link
Member

@tobiasehlert I have finished some refactoring and tested by deploying main branch and then running a plan with this branch to ensure it does not attempt to change anything. If you are happy with these changes, I will merge to a release branch, so I can run the e2e tests.

@jaredfholgate jaredfholgate changed the base branch from main to release/feat-firewall-multiple-public-ip-config-support June 24, 2025 11:48
@jaredfholgate jaredfholgate merged commit 22ef715 into Azure:release/feat-firewall-multiple-public-ip-config-support Jun 24, 2025
13 of 14 checks passed
@jaredfholgate
Copy link
Member

Moved to a release branch

jaredfholgate added a commit that referenced this pull request Jun 24, 2025
Co-authored-by: Tobias Lindberg <tobias.ehlert@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Maintainers need to triage still
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for one hub network to have multiple firewall custom public IP addresses
2 participants