Reference shared bicep module by major version from the Azure Container Registry

[astro-phage]

It would be great if you could reference a shared bicep module by a major version (tag) from the Azure Container registry.

Example:

Versions in ACR:

• myregistry.azurecr.io/bicep/myappmodule:v1.0.25798
• myregistry.azurecr.io/bicep/myappmodule:v1.0.25799

main.bicep:

module appService 'br:myregistry.azurecr.io/bicep/myappmodule:v1' = {
  name: 'appService'
  params: {
    ...
  }
}

So, in this case, version v1.0.25799 would be used. Minor changes to the shared module could be deployed without having to edit the version in the referencing bicep files. Nevertheless, all changes will be versioned properly in ACR.

[brwilkinson]

Adding a few open issues relating to the Bicep registry:

• List available tags/versions when using/referencing a module #4920
• Support wildcards in defining versions used for bicep registry modules and template spec modules #4186 <-- this one specifically relates the above request.
• Support for defining registry modules and template spec modules as variables #4185

[astro-phage]

Thanks a lot!