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

Azure Firewall with Virtual Hub deployment fails as unable to set Public IP #219

Closed
chris5287 opened this issue Apr 27, 2022 · 4 comments · Fixed by #226
Closed

Azure Firewall with Virtual Hub deployment fails as unable to set Public IP #219

chris5287 opened this issue Apr 27, 2022 · 4 comments · Fixed by #226
Assignees

Comments

@chris5287
Copy link

address: (parVirtualHubEnabled && parAzureFirewallEnabled) ? modAzureFirewallPublicIP.outputs.outPublicIPID : ''

This does not work with Virtual Hubs, it appears the Public IP is a read only resource that gets randomly allocated?

@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Apr 27, 2022
@jtracey93 jtracey93 self-assigned this Apr 27, 2022
@jtracey93
Copy link
Collaborator

Hey @chris5287,

Thanks for raising this. Aware we are speaking on Friday on a call.

However, I have just tested this and it worked for me (also we test all PRs so had me a little concerned how may of this one slipped by 😁):
image

Can you share some more info around any customizations you made and what the error is/was?

Thanks

Jack

@jtracey93 jtracey93 added Needs: Author Feedback and removed Needs: Triage 🔍 Needs triaging by the team labels Apr 27, 2022
@chris5287
Copy link
Author

The issue occurs on the 2nd deployment, as the initial deployment seems to ignore the value provided.

If you check your deployment you should see the Public IP against the Azure Firewall does not match the one that was provisioned?

@ghost ghost added Needs: Attention 👋 Needs attention from the maintainers and removed Needs: Author Feedback labels Apr 27, 2022
@jtracey93
Copy link
Collaborator

The issue occurs on the 2nd deployment, as the initial deployment seems to ignore the value provided.

If you check your deployment you should see the Public IP against the Azure Firewall does not match the one that was provisioned?

Thanks will investigate in the morning 👍

@jtracey93
Copy link
Collaborator

Thanks @chris5287 you are indeed correct about the 2nd deployment and the public IP not being used.

I am working on a fix for this as we speak and hope to get out soon 👍

@jtracey93 jtracey93 removed the Needs: Attention 👋 Needs attention from the maintainers label Apr 29, 2022
@ghost ghost added the Status: Fixed label May 5, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jun 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants