Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow to unset env variables
See original GitHub issueecho 'SOME_VAR=some-value' >> $GITHUB_ENV can be used to set an environment variable for subsequent steps, but there seems to be no documented way to unset it.
Note that echo 'SOME_VAR=' >> $GITHUB_ENV will set it to the empty value, but that’s different from not having the variable set at all.
Rationale: In some workflows, it might be necessary to checkout and/or run untrusted code. At that point I’d like to clean up as much sensitive values as possible. Unsetting env vars (like SSH_AGENT_PID or SSH_AUTH_SOCK) is part of this.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:21
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep, that’d also be my use case. The problem for me is that environment variables exported by
aws-actions/configure-aws-credentialsalways have a higher precedence in the AWS CLI credentials chain than if I were to setAWS_PROFILE.I’m facing the same issue - I need to cleanup AWS creds from the
aws-actions/configure-aws-credentialsstep but don’t know how to do it properly.