You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring a custom script on a VMSS, it is explicitly using a SAS token for the storage account. This SAS code seems to expire after about a day. On top of that, when using this module for a self-hosted agent I am facing many issues, especially with the custom script. This needs to be addressed. Also there should be a way to add the devops extension via code as well (see below). While it isn't necessary since devops automatically configures it - it would be nice.
Describe the bug
When configuring a custom script on a VMSS, it is explicitly using a SAS token for the storage account. This SAS code seems to expire after about a day. On top of that, when using this module for a self-hosted agent I am facing many issues, especially with the custom script. This needs to be addressed. Also there should be a way to add the devops extension via code as well (see below). While it isn't necessary since devops automatically configures it - it would be nice.
// resource resDevOpsAgent 'Microsoft.Compute/virtualMachineScaleSets/extensions@2021-07-01' = {
// name: 'Microsoft.Azure.DevOps.Pipelines.Agent'
// parent: resVirtualMachineScaleSet
// properties: {
// publisher: 'Microsoft.VisualStudio.Services'
// type: 'TeamServicesAgent'
// typeHandlerVersion: '1.31'
// autoUpgradeMinorVersion: false
// }
// }
To reproduce
Run code below and add a document to the storage account. Configure a devops agent using this vmss.
Code snippet
Relevant log output
No response
The text was updated successfully, but these errors were encountered: