Bicep ACR registry namespaces

[cloudfright]

Hi all,

I was wondering what the collective wisdom is around namespaces in Bicep ACR registries?

Instead of reinventing the wheel, would it make sense to follow the {provider-namespace}/{resource-type} pattern we see in the ARM template reference?

e.g. something like this: (ensuring names are lower case and spaces are replaced with hyphens)

• yourorgacr.azurecr.io/bicep-modules/microsoft.storage/storageaccounts/blob-services:1.0.3
• yourorgacr.azurecr.io/bicep-modules/microsoft.keyvault/vaults:2.6.7
• yourorgacr.azurecr.io/bicep-modules/microsoft.sql/servers/databases:1.0.4

This could possibly be a reasonable approach given it's the pattern we see when we create a resource in a Bicep file and could exhibit less cognitive load.

What have people tried and what's worked well?

Thanks!

[thepaulmacca]

Still trying to work on the best approach for this myself, so am interested to hear suggestions from others on what they're doing

The above looks good to me though, similar to what they're doing in the ResourceModules repo

[brwilkinson]

That is exactly what came to mind for me, thinking about the ResourceModules repo.

FYI

• https://github.com/Azure/ResourceModules
• https://github.com/azure/ResourceModules/wiki <-- getting started wiki

I think if you design your module around that philosophy that will work very well. following the provider type hierarchy.

Personally, I opt for a solution-based approach to Modules.

Some examples:

• I didn't list out all of the different things in each of these, however it's a mix of resource types that makes an overall solution.

  • VM - https://github.com/brwilkinson/AzureDeploymentFramework/blob/main/ADF/bicep/VM.bicep
    • a list of mixed resource types
  • Azure Image Builder - https://github.com/brwilkinson/AzureDeploymentFramework/blob/main/ADF/bicep/ImageBuilder.bicep
    • a list of mixed resource types
  • cloudshell on a VNET - https://github.com/brwilkinson/AzureDeploymentFramework/blob/main/ADF/bicep/CloudShellRelay.bicep
    • a list of mixed resource types, examples listed
      • existing virtual network reference
      • existing subnet reference
      • relay namespace
      • network profile
      • private link for the relay
      • private link DNS registration for the private link