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

set-output and save-state are deprecated #252

Closed
muffl0n opened this issue Oct 12, 2022 · 6 comments
Closed

set-output and save-state are deprecated #252

muffl0n opened this issue Oct 12, 2022 · 6 comments

Comments

@muffl0n
Copy link

muffl0n commented Oct 12, 2022

Since runner version 2.298.2 set-output and save-state are deprecated: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
@dawrobel
Copy link

Have the same issue. Seems to be that terraform init|plan|apply triggering warnings once set from hashicorp/setup-terraform@v2 inside workflow

@magnetikonline
Copy link
Contributor

Once tests are passing here and merged #247 this warning will vanish.

@actions/core 1.10.0 handles set-output using the new environment file mode - not outputting to STDOUT.

@piotrekkr
Copy link

We need to wait and it should be done soon. As a temp fix I used terraform_wrapper: false because I did not need this wrapper stuff

@muffl0n
Copy link
Author

muffl0n commented Nov 1, 2022

Fixed in #247, released in v2.0.3. Thank you very much! ❤️

@kallangerard
Copy link

fixes #306

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants