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

Warning: set-env command is deprecated #22

Closed
mbtools opened this issue Oct 11, 2020 · 7 comments
Closed

Warning: set-env command is deprecated #22

mbtools opened this issue Oct 11, 2020 · 7 comments

Comments

@mbtools
Copy link

mbtools commented Oct 11, 2020

During azure/aci-deploy@v1 you get the following warning.

https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

image

@nosvalds
Copy link

Adding that is an Error now, and will be disabled on November 16th

Run azure/aci-deploy@v1
26
Error: The `set-env` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

@remyjette
Copy link

November 16th has passed and the error has now changed:

Error: Unable to process command '::set-env name=AZURE_HTTP_USER_AGENT::' successfully.
Error: 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/

@remyjette
Copy link

remyjette commented Nov 17, 2020

set-env was being used by @actions/core, which aci-deploy relies on.
@actions/core resolved the issue in actions/toolkit#571.

I just tested forking this repo and upgrading to @actions/core 1.2.6 (latest), and the error goes away. Published #27 to upgrade it here. Merging #18 should resolve this issue.

@mitsha-microsoft
Copy link
Member

#18 is merged. I think it should resolve this issue

@WardMaes
Copy link

The error is still showing, preventing deployments.

@remyjette
Copy link

A new version of the action will need to be created first. See #26

@JoeMarkov
Copy link

My deployments are down due to this, any plan when this can be fixed?

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

Successfully merging a pull request may close this issue.

6 participants