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

PowerShell module to support deploying into an existing virtual network #1337

Open
philipstreet opened this issue Feb 21, 2025 · 0 comments
Open
Labels
Needs: Triage 🔍 Untriaged issue needs to be reviewed

Comments

@philipstreet
Copy link

philipstreet commented Feb 21, 2025

⚠️ Problem

The Microsoft documentation says you can create your own vnet & peering to use for a FinOps Hub (https://learn.microsoft.com/en-gb/cloud-computing/finops/toolkit/hubs/private-networking#finops-hub-virtual-network) but the toolkit does not appear to provide the ability to deploy/upgrade a FinOps Hub into an existing vnet. Have I missed something?

🛠️ Solution

Update Deploy-FinOpsHub command with additional parameters to allow the user to specify:

  • the resource group & virtual network (or resourceID) to be used by the FinOps Hub.
  • resourceIDs of Private DNS Zones to be linked to the Private Endpoints created on deployed resources.

ℹ️ Additional context

My company has strict controls on who/how virtual networks, peering & Private DNS Zones are created, so these cannot be performed by 3rd-party toolkits.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.
@philipstreet philipstreet added the Needs: Triage 🔍 Untriaged issue needs to be reviewed label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Untriaged issue needs to be reviewed
Projects
None yet
Development

No branches or pull requests

1 participant