-
Notifications
You must be signed in to change notification settings - Fork 113
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
[Bug]: Deploy to Environment #1136
Comments
Looks like a bug. If you change to use microsoft/AL-Go-PTE@main -. I assume it works then? |
I changed it to use microsoft/AL-Go-PTE@main and yes, it is working. I also have the AZURE_CREDENTIALS defined with access to a keyvault and am using the keyvault for secrets, but not for the environment secrets. |
The reason for this issue is that this powershell command: Get-AzKeyVaultSecret -VaultName "BuildVariables" -Name 'UAT-AUTHCONTEXT' will return the secret if it exists or null if it doesn't, whereas this command Get-AzKeyVaultSecret -VaultName "BuildVariables" -Name 'UAT_AUTHCONTEXT' Will throw due to an illegal secret name. GitHub secrets allows '_', but not '-' Therefore, we look for both, but it obviously shouldn't throw. |
Shipped in preview |
Using: AL-Go-Preview (current)
We have environments configured in GitHub (UAT, for instance) and have an environment secret "AUTHCONTEXT" created with the proper Json in there. However, when we run the CI/CD pipeline, it throws the following errors when trying to deploy the apps to the environment.
Did anything change in the way this is working or has to be defined? It used to work (not sure exactly when last).
The text was updated successfully, but these errors were encountered: