While it's possible to use a managed identity to run a script stored in blob storage. it's limited to just a script.
In our build process we need to download a number of ZIP and installers from BLOB. his makes it so we have to pass in the SAS token as part of the customizer. and due to the short life time on a SAS token. the Image template has to be recreated every run.
We would like to avoid the constant template deletion and creation process.
Hi, we have an open item on our backlog make the user identity available to the build VM, this means you can use it to connect to Azure storage, will this help?
While it's possible to use a managed identity to run a script stored in blob storage. it's limited to just a script.
In our build process we need to download a number of ZIP and installers from BLOB. his makes it so we have to pass in the SAS token as part of the customizer. and due to the short life time on a SAS token. the Image template has to be recreated every run.
We would like to avoid the constant template deletion and creation process.