We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
set-env
I tried re-running the pipeline (after Initializing-KeyVault) using GitHub actions.
I got this error when deploying to Dev:
The set-env command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
ACTIONS_ALLOW_UNSECURE_COMMANDS
true
However, when I run this pipeline in Azure DevOps, it deploys to DEV, QA, and PROD with no issue.
Any guidance?
The text was updated successfully, but these errors were encountered:
Update Download Keyvaylt version from uses: Azure/get-keyvault-secrets@v1.0 --> uses: Azure/get-keyvault-secrets@v1 It will fix the issue.
- name: Download KeyVault Secrets uses: Azure/get-keyvault-secrets@v1
Sorry, something went wrong.
No branches or pull requests
I tried re-running the pipeline (after Initializing-KeyVault) using GitHub actions.
I got this error when deploying to Dev:
The
set-env
command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting theACTIONS_ALLOW_UNSECURE_COMMANDS
environment variable totrue
. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/However, when I run this pipeline in Azure DevOps, it deploys to DEV, QA, and PROD with no issue.
Any guidance?
The text was updated successfully, but these errors were encountered: