Open scrocquesel-ml150 opened 2 weeks ago
@vhvb1989 can we make agent/pool name Default
configurable?
Yes, I will take a look. We should be able to check if more than one and list them to ask user to pick which to use
@vhvb1989 can't we infer this from being defined in the azdo pipeline yaml? - https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/pool?view=azure-pipelines#pool-string
@vhvb1989 can't we infer this from being defined in the azdo pipeline yaml? - https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/pool?view=azure-pipelines#pool-string
We could, but sometimes projects won't have a pipeline definition, or they could have one which only defines a pool and vmImage (i.e. Ubuntu). So trying to get the pool name from the definition will not work for all scenarios.
The agent pool name can be defined in the pipeline definition to override the default agent pool used and assigned to the pipeline when the pipeline was created...
Output from
azd version
azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)Describe the bug Running
azd pipeline config --provider azdo
fails withThe name of the agent queue is hard coded
https://github.com/Azure/azure-dev/blob/a17935e47211ed01780281974c6d63b467de5b14/cli/azd/pkg/azdo/pipeline.go#L48
To Reproduce N/A
Expected behavior We are able to give the name of the queue to use and the config passes.
Environment N/A
Additional context My agent queue is named
Azure Pipelines