无法授权 Azure 订阅在基于 YAML 的管道中使用
Unable to authorize Azure Subscription for use within YAML based pipeline
已从头开始创建基于 Azure DevOps YAML 的管道,需要使用 Azure 订阅。订阅值已存储在 Key Vault 中,然后链接到变量组。 Pipeline 可以以不显眼的方式访问变量组和链接的 Key Vault。但是,管道执行失败并出现管道无权访问所需订阅的错误。当订阅值移动到变量组时,问题仍然存在。当订阅值被声明为管道变量时,问题就消失了。单击错误旁边的授权按钮对解决问题没有帮助。
- stage: 'DeployDevelopment'
displayName: ''
dependsOn: Build
jobs:
- deployment: DeployDevelopment
pool:
vmImage: 'ubuntu-latest'
environment: Development
variables:
- group: Secrets
- group: Release
strategy:
runOnce:
deploy:
steps:
- task: AzureRmWebAppDeployment@4
displayName: ''
inputs:
azureSubscription: '$(ConnectedServiceName)'
appType: 'webAppLinux'
WebAppName: '$(DevEnvironemntWebAppName)'
packageForLinux: '$(Pipeline.Workspace)/app/s'
RuntimeStack: 'NODE|10-lts'
StartupCommand: '$(StartupCommand)'
WebConfigParameters: '-Handler iisnode -NodeStartFile server.js -appType node'
AppSettings: '-WEBSITE_NODE_DEFAULT_VERSION 10.12.0'
Thanks for reporting the issue on Developer Community. Azure key vault
values are fetched at run time. The resource are authorized before
deployment. Pipeline can;t be authorized for a value that is not
available. Hence this is not supported. scenario.
已从头开始创建基于 Azure DevOps YAML 的管道,需要使用 Azure 订阅。订阅值已存储在 Key Vault 中,然后链接到变量组。 Pipeline 可以以不显眼的方式访问变量组和链接的 Key Vault。但是,管道执行失败并出现管道无权访问所需订阅的错误。当订阅值移动到变量组时,问题仍然存在。当订阅值被声明为管道变量时,问题就消失了。单击错误旁边的授权按钮对解决问题没有帮助。
- stage: 'DeployDevelopment'
displayName: ''
dependsOn: Build
jobs:
- deployment: DeployDevelopment
pool:
vmImage: 'ubuntu-latest'
environment: Development
variables:
- group: Secrets
- group: Release
strategy:
runOnce:
deploy:
steps:
- task: AzureRmWebAppDeployment@4
displayName: ''
inputs:
azureSubscription: '$(ConnectedServiceName)'
appType: 'webAppLinux'
WebAppName: '$(DevEnvironemntWebAppName)'
packageForLinux: '$(Pipeline.Workspace)/app/s'
RuntimeStack: 'NODE|10-lts'
StartupCommand: '$(StartupCommand)'
WebConfigParameters: '-Handler iisnode -NodeStartFile server.js -appType node'
AppSettings: '-WEBSITE_NODE_DEFAULT_VERSION 10.12.0'
Thanks for reporting the issue on Developer Community. Azure key vault values are fetched at run time. The resource are authorized before deployment. Pipeline can;t be authorized for a value that is not available. Hence this is not supported. scenario.