Skip to content
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

The set-env command is disabled when running in GitHub Actions #5

Open
slsu0424 opened this issue Feb 11, 2022 · 1 comment
Open

The set-env command is disabled when running in GitHub Actions #5

slsu0424 opened this issue Feb 11, 2022 · 1 comment

Comments

@slsu0424
Copy link

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/

However, when I run this pipeline in Azure DevOps, it deploys to DEV, QA, and PROD with no issue.

Any guidance?

@sumitraj0103
Copy link

Update Download Keyvaylt version from uses: Azure/get-keyvault-secrets@v1.0 --> uses: Azure/get-keyvault-secrets@v1
It will fix the issue.

Download KeyVault Secrets

- name: Download KeyVault Secrets
  uses: Azure/get-keyvault-secrets@v1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants