Open Menghua1 opened 1 month ago
@jongio Yes, this issue can also be reproduced in main. We tested the following four scenarios and they can all be reproduced:
todo-nodejs-mongo-aks
.main
branch + azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba7dcc5b3f7e883213a2315a8b275294def). main
branch + azd version 1.11.0-beta.1-pr.4140256 (commit b6402defbf4c4210855e14c114988010e0a51ed7). staging
branch + azd version 1.11.0-beta.1-daily.4152592 (commit e2ff8ba7dcc5b3f7e883213a2315a8b275294def). staging
branch + azd version 1.11.0-beta.1-pr.4140256 (commit b6402defbf4c4210855e14c114988010e0a51ed7).@wbreza remember seeing similar issue on the ai starters due to User vs ServicePrincipal? cc @vhvb1989
@rajeshkamal5050 In the latest round of azd manual testing, this issue still exists.
todo-nodejs-mongo-aks
.staging
.@rajeshkamal5050 and @jongio In the latest round of azd manual testing, this issue still exists.
todo-nodejs-mongo-aks
.staging
.Looks like AZURE_PRINCIPAL_TYPE is not set during azd pipeline config
and it is empty during CI run, making the runner to take the value of the literal ${AZURE_PRINCIPAL_TYPE} instead of replacing it with a value from the env.
This is an issue in the template configuration. The azure.yaml should define the AZURE_PRINCIPAL_TYPE in the pipeline->variables as a required ENV VAR to set during azd pipeline config
@rajeshkamal5050 In the latest round of azd manual testing, this issue still exists.
todo-nodejs-mongo-aks
.staging
.DevContainer
.
Describe the issue: Running the
azd pipeline config --provider azdo
command fails with the following error message:Repro Steps:
azd auth login
.azd init -t todo-nodejs-mongo-aks -b staging
.azd pipeline config --provider azdo
.Environment:
todo-nodejs-mongo-aks
.staging
Expected behavior:
azd pipeline config --provider azdo
commands can be run successfully.@jongio for notification.