-
Notifications
You must be signed in to change notification settings - Fork 129
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
[Question]: What is causing the issue in Az.KeyVault? and How we can resolve it? #1424
Comments
You are using a very old version of AL-Go for GitHub I think what happened here is that the GitHub runners have a different version of various modules installed and v4.1 of AL-Go doesn't work with future installed bits. If your GhTokenWorkflow secret is in Azure KeyVault - you might need to create the secret in GitHub to run the Update AL-Go system Files. |
The error in the build will be the same until you have successfully run and merged updates to AL-Go System Files. You might need to remove the Azure_Credentials secret (or if it is an organizational secret - remove access from the repo) - and then create the GhTokenWorkflow secret in the repository. |
You need to merge the pull request, then the next build from your main branch should be fine |
Did this solve the issue? |
Hi Freddy, Yes, it is fixed now, thank you very much for your assistance. |
Good Morning @freddydk We came across the same issue, we followed your steps and the "Read Secrets" works, but now we have an issue with the Codesigning(DigiCert in Azure Key Vault) of the Extension as we had to remove the Azure_Credentials form the Repo's secrets. Where must one define the Azure_Credentials now if one has the Codesign Cert in Azure Key Vault ? |
@bernhardpluteo - once you have updated AL-Go System Files, I think everything should work fine and you can put the secret back |
Question
Hi
Last 2weeks, we can build perfectly fine.
but when tried it again last night, this happened
May, we know what was the cause of this issue, and how we can resolve it?
The text was updated successfully, but these errors were encountered: