Open diberry opened 1 month ago
Ah I saw that on CI. I'll try to replicate locally. It shouldnt need az CLI.
Replicated, darn. I was testing outside of the dev container, where I must have been logged in with the Azure CLI. The new Promptflow SDK calls DefaultAzureCredential behind the scenes, and is doing it in some way that's not working with azd login. I'm looking into it.
Sent PR to PromptFlow SDK: https://github.com/microsoft/promptflow/pull/3244
@pamelafox do I need to set azd config set auth.useAzCliAuth "true"
before azd up
?
No, you would need to use the actual Azure CLI to login, so that DefaultAzureCredential would use the Azure CLI credential. Promptflow's usage of DefaultAzureCredential isn't compatible with the Azure Developer CLI credential. The azd login is still fine for the azd up process.
My PR was merged, so I am awaiting the release of the new SDK. But I can add the Azure CLI to this container for now and a step to login, since that might take a few days.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
python3 -m scripts generate --output=my_input/qa.jsonl --numquestions=14 --persource=2
python3 -m scripts evaluate --config=my_config.json --numquestions=14
with the following my_config.jsonazd config set auth.useAzCliAuth "true"
thenazd auth login
again and az cli isn't in repo.Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions
Mention any other details that might be useful