bicep
bicep copied to clipboard
possibility to call module from registry with version stored in variable
Is your feature request related to a problem? Please describe. Now it is not possible to call a module from registry with specified version in a variable
var version = '0.0.1'
module mod_webapp 'br/CoreModules:mod_webapp:${version}' = {
name: 'deployment-mod_webapp'
...
}
Describe the solution you'd like I would like to store the module version in the variable or param.
I thought we had another issue about this, but I can't find it. This is feasible with variables, but not with parameters, since parameter values are not known until deployment and that could change the module code that needs to be validated.
Related: #413
I also have a use case where the path to the ACR and the version of the Bicep module need to be defined as parameters that are leveraged by an Azure DevOps pipeline when deploying/updating infrastructure.
Specifying the name of the ACR as a parameter would be indeed valuable as you wouldn't need to update every template when you migrate to another container registry.
Specifying the name of the ACR as a parameter would be indeed valuable as you wouldn't need to update every template when you migrate to another container registry.
@jhueppauff - specifically for this case, we would recommend adding an alias to bicepconfig, and if you ever change the ACR URL, you would only need to change the value in bicepconfig: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config-modules#aliases-for-modules
Any news about this feature request plz ? I still have "Error BCP092: String interpolation is not supported in file paths."
Hi maxinthecloud, this issue has been marked as stale because it was labeled as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thanks for contributing to bicep! :smile: :mechanical_arm:
could this please be reopened? I would really like this enhancement as we can tokenize our paths.
Re-opening and renaming to cover variables specifically, since that's much easier than params.
We are a large team of developers in my company that would appreciate this feature immensely as we address different versions of bicep modules hosted in an ACR. Pretty please, save us :)
This would be very useful. I have a UAT and a Production container registry for modules, and being able to set the path would be useful