build/bake: support GCP WIF registry identities#244
Open
crazy-max wants to merge 1 commit into
Open
Conversation
crazy-max
force-pushed
the
identities-gcp
branch
2 times, most recently
from
July 23, 2026 14:29
0200bc8 to
17abd8a
Compare
crazy-max
marked this pull request as ready for review
July 23, 2026 14:30
crazy-max
force-pushed
the
identities-gcp
branch
from
July 23, 2026 14:34
17abd8a to
52bdf65
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
identities-gcp
branch
from
July 23, 2026 14:54
52bdf65 to
3cc39de
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #146
needs #243This adds Google Artifact Registry support to the
registry-identitiesflow introduced in #243.The shared registry identity parser now accepts
type: gcp-wifwith a registry host, Workload Identity Provider, service account, and project ID. The reusablebuild.ymlandbake.ymlworkflows usegoogle-github-actions/authto request an access token in the same job that needs registry access, then pass that token directly todocker/login-actionwith theoauth2accesstokenusername.This lets callers push to Google Artifact Registry through GitHub OIDC and GCP Workload Identity Federation without storing long-lived registry credentials. The access token is not passed through reusable workflow outputs or caller secrets, and provider-specific authentication remains pinned and controlled inside GitHub Builder.