Workflows: Token generation as a step rather than a job #32868
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While #32849 correctly moved authentication to a GitHub App generated token, it did not take into account another caveat to Actions: job outputs that contain sensitive data are dropped and not emitted by runners. This PR moves token generation to a step within the jobs that need it to overcome this.
Relations
Relates #32849
References
Output from Acceptance Testing
N/a, Actions