-
Notifications
You must be signed in to change notification settings - Fork 210
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
fix: Azure BYOCNI workflow #2546
Conversation
ef3d492
to
155c668
Compare
This PR introduces a couple of fixes: 1. Workaround for the Azure BYOCNI workflow: asynchronous Azure OIDC token fetch to avoid token assertion issues. 2. Azure location changed to the `eastus2` that used less intensive. Signed-off-by: viktor-kurchenko <[email protected]>
155c668
to
ea2d18d
Compare
ea2d18d
to
be41d21
Compare
@michi-covalent I think you can mark the |
|
Due to the |
token=$(curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "${ACTIONS_ID_TOKEN_REQUEST_URL}&audience=api://AzureADTokenExchange" | jq .value -r) | ||
az login --service-principal -u ${{ secrets.AZURE_PR_CLIENT_ID }} -t ${{ secrets.AZURE_PR_TENANT_ID }} --federated-token $token --output none | ||
# Sleep for 4 minutes | ||
sleep 240 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not 242?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we achieve this with a periodic check for availability and a nice message when the failure is due to timeout?
EDIT: Ah never mind, I see that the overall step is doing the loop every 4 mins. I expected a much quicker loop.
This PR introduces a couple of fixes:
eastus2
that used less intensive.Workflow run example: https://github.com/cilium/cilium-cli/actions/runs/9063109497/job/24898372774?pr=2546
Workaround for: #2478