Skip to content

feat(workflows): forward the S3 cache secrets through the generic and Python deploys - #368

Merged
JesperTerkelsen merged 1 commit into
mainfrom
feat/forward-s3-secrets
Oct 1, 2026
Merged

JesperTerkelsen merged 1 commit into
mainfrom
feat/forward-s3-secrets

Conversation

@JesperTerkelsen

Copy link
Copy Markdown
Member

What?

deploy-generic, deploy-generic-v2 and deploy-python accept the optional GH_ACTION_ACCESS_KEY_ID / GH_ACTION_SECRET_ACCESS_KEY secrets and forward them to component-build, as deploy-kotlin(-v2) already does.

Why?

Since #367 these deploys build their images on ARC. component-build keeps Dockerfile cache mounts in S3 when it gets these secrets, and in the slower GitHub cache otherwise. Callers of these three workflows had no way to pass them: passing a secret the called workflow doesn't declare is invalid. This unblocks the per-repo PRs that add them.

Optional and backwards compatible.

nojira

🤖 Generated with Claude Code

… Python deploys

deploy-generic, deploy-generic-v2 and deploy-python accept the optional
GH_ACTION_* secrets and pass them to component-build, so their image
builds on ARC can keep Dockerfile cache mounts in S3 like deploy-kotlin.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@JesperTerkelsen
JesperTerkelsen marked this pull request as ready for review October 1, 2026 07:42
@JesperTerkelsen
JesperTerkelsen requested a review from a team as a code owner October 1, 2026 07:42
@JesperTerkelsen
JesperTerkelsen requested review from chandrashekar-dhar and removed request for a team October 1, 2026 07:42
@JesperTerkelsen
JesperTerkelsen merged commit 4920a62 into main Oct 1, 2026
1 check passed
@JesperTerkelsen
JesperTerkelsen deleted the feat/forward-s3-secrets branch October 1, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants