-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue] AZURE_CREDENTIALS not set in new Github workflow, login fails #1399
Comments
Update: I looked through the azd code and have a better understanding of the issue. I was getting an error on
That's because there is no AZURE_CREDENTIALS secret, and that's because Github pipeline config defaults to FCIS: Is there guidance on how to update workflow for fcis? The latest release notes recommend an incompatible login flow:
|
Ah I see the official samples use a more complex workflow than whats suggested in the release notes, to account for both auth types:
Can someone update the release notes, please? This appears to be the full diff needed: |
@wbreza can you take a look and update release notes as needed? |
Updated release notes with instructions on the required updates for your github workflow depending whether you are using Client Credentials or Federated Credentials |
Output from
azd version
Whatever's in mcr.microsoft.com/azure-dev-cli-apps:latest
Output from
az version
N/A
Describe the bug
I updated my Github workflow to use the new login scheme, re-ran azd pipeline config locally on the very latest azd (azd version 0.5.0-beta.3), and pushed the Github secrets.
Unfortunately, the azd provision stage is ending in:
You can see the full output here, I even added --debug flag to help:
https://github.com/pamelafox/msdocs-django-postgresql-sample-app-azd/actions/runs/3925438619/jobs/6710359802
To Reproduce
Expected behavior
I expected a successful deploy. I ported a very similar repo today as well (https://github.com/pamelafox/msdocs-flask-postgresql-sample-app-azd), and its workflows are fine, which is why I'm really flummoxed by this issue.
The text was updated successfully, but these errors were encountered: