Closed stoilovkr closed 1 month ago
It may be a bug because when reverted to main version of Al-Go, Sign step passed successfully with no secrets change.
I assume that the GitHub secret you mention is AZURE_CREDENTIALS and not AUTHCONTEXT - right? Yes, this is a bug in preview
I assume that the GitHub secret you mention is AZURE_CREDENTIALS and not AUTHCONTEXT - right? Yes, this is a bug in preview
It was working with the AZURE_CREDENTIALS secret, but then when it started failing, I inspected the source code, and it seemed like it's pulling the data from AUTHCONTEXT secret, so I copied the same value in that secret too, but it was failing again.
I assume that the GitHub secret you mention is AZURE_CREDENTIALS and not AUTHCONTEXT - right? Yes, this is a bug in preview
It was working with the AZURE_CREDENTIALS secret, but then when it started failing, I inspected the source code, and it seemed like it's pulling the data from AUTHCONTEXT secret, so I copied the same value in that secret too, but it was failing again.
Sorry I inspected the documentation here where it says that the secret should be AUTHCONTEXT. So, you might need to update the documentation to say AZURE_CREDENTIALS if it's wrong.
Will fix the documentation on that (copy/paste error) - this is under the section called Azure_Credentials -> Connect to Azure
AuthContext is used for deployments only.
Shipped in preview
Question
When running CI/CD action, on step Sign I get the following error:
I have a Github secret in the following format:
AUTHCONTEXT: {"keyVaultName":"REDACTED","clientId":"REDACTED","clientSecret":"REDACTED","tenantId":REDACTED"}
What am I missing here to make the action use app registration with client secret instead of managed identity with federated token? I am using preview version of AL-Go.