Configure gcloud auth id-token permissions for nested workflow #1331
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t0yv0
approved these changes
Jan 29, 2025
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 30, 2025
Followup to #1331 which was supposed to fix pulumi/pulumi-gcp#2919 but instead pushed the permissions problem up into the next parent Workflow. Upshot is that the "invalid Workflow" error happens in a different file: https://github.com/pulumi/pulumi-gcp/actions/runs/13042448162/workflow#L101 I believe this is all of the places where we need to tell Actions to inherit slightly elevated permissions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes pulumi/pulumi-gcp#2919.
It looks like when you nest Workflows, you also need to state elevated permissions at the parent Workflow level.