-
Notifications
You must be signed in to change notification settings - Fork 509
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
export_default_credentials should place credentials outside of the workspace #144
Comments
Hi @travisgroth The credentials have to be in a shared location in order for authentication to work across steps. In our testing, GitHub Actions cleared the temporary directory between steps (even when documentation said it would be persisted). |
Hey @sethvargo thanks for the quick response. I suppose it doesn't matter if it's the As far as the |
👍 |
Hi @sethvargo |
TL;DR
GOOGLE_APPLICATION_CREDENTIALS should be stored in the action temporary directory, not in the checked out repository. Doing so creates a dirty git state.
Expected behavior
git state is not dirty after exporting GOOGLE_APPLICATION_CREDENTIALS.
Observed behavior
git state is dirty and shows up in automatic version detection and other release automation tools. https://goreleaser.com/, for instance, will hard fail if git state is dirty during a non-snapshot release.
Reproduction
Action YAML
Repository
https://github.com/pomerium/pomerium/runs/891636795#step:9:31
Additional information
No
The text was updated successfully, but these errors were encountered: