[BICEP] Add support for custom resource naming in FinOps Toolkit

[Copilot]

Overview

This PR adds support for custom resource naming in the FinOps Toolkit Bicep deployment, allowing organizations to follow their naming standards when deploying FinOps resources.

Changes Made

• Added new parameters to main.bicep:
  • storageAccountName: Custom name for the Storage Account
  • dataFactoryName: Custom name for the Data Factory
  • keyVaultName: Custom name for the Key Vault
• Updated the parameter chain to pass these values through hub.bicep and hub-app.bicep
• Modified the name generation logic in hub-types.bicep to use custom names when provided, falling back to the auto-generated names for backward compatibility

Example Usage

With these changes, consumers can specify their own resource names:

module finopsHub 'br/public:finops/hub:latest' = {
  name: 'finopsHub'
  params: {
    hubName: 'prod-finops'
    storageAccountName: 'companyfinopsdata001'
    dataFactoryName: 'company-finops-ingestion-001'
    keyVaultName: 'company-finops-vault-001'
  }
}

Or use a company naming module:

module finopsHub 'br/public:finops/hub:latest' = {
  name: 'finopsHub'
  params: {
    hubName: 'prod-finops'
    storageAccountName: naming.storageAccount('finops-data')
    dataFactoryName: naming.dataFactory('finops-engine')
    keyVaultName: naming.keyVault('finops-vault')
  }
}

Backward Compatibility

All parameters have empty string defaults, ensuring backward compatibility with existing deployments. When a parameter is not specified, the resource name is generated using the original logic based on the hub name.

Fixes #1105.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: bicep build src/templates/finops-hub/main.bicep (dns block)
  • Triggering command: bicep build src/templates/finops-hub/modules/hub-types.bicep (dns block)
  • Triggering command: bicep build src/templates/finops-hub/modules/hub-app.bicep (dns block)
• app.aladdin.microsoft.com
  • Triggering command: /usr/bin/../../opt/az/bin/python3 -Im azure.cli bicep build --file src/templates/finops-hub/main.bicep --force (dns block)
• cdn.fwupd.org
  • Triggering command: /usr/bin/fwupdmgr refresh (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[flanakin]

Revert

[Copilot]

Reverted the parameter pass-through in main.bicep (commit 66f9c8f)

[flanakin]

Revert

[Copilot]

Reverted the custom resource naming parameters in main.bicep (commit 66f9c8f)

[flanakin]

Revert this file

[Copilot]

Removed this file as requested (commit 66f9c8f)

[flanakin]

Revert this file

[Copilot]

Removed this file as requested (commit 66f9c8f)

[flanakin]

@copilot You reverted too much. The storage, ADF, and Key Vault names should be specified in hub.bicep and passed down to hub-app.bicep.

[Copilot]

I've restored the storage, ADF, and Key Vault name parameters in hub.bicep and hub-app.bicep while ensuring they're properly passed through the module chain. The parameters are now available in hub.bicep and passed down to hub-app.bicep as requested (commit 3cb5af8).

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: bicep build src/templates/finops-hub/modules/hub.bicep (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list