Skip to content

ci: mint PlanetScale credentials over OIDC instead of storing tokens - #2553

Merged
Makisuo merged 3 commits into
mainfrom
ci/planetscale-oidc
Nov 14, 2026
Merged

Makisuo merged 3 commits into
mainfrom
ci/planetscale-oidc

docs: pin the restore drill's PlanetScale trust to its workflow

f4bd8e8
Select commit
Loading
Failed to load commit list.
Maple Review Bot / Maple / review succeeded Nov 14, 2026 in 29s

Confidence 10/10 · No issues found

🟢 Confidence 10/10 · safe to merge. Delta since the last review is two docs files, which are out of scope; the OIDC exchange itself is unexercised until the post-merge deploy and dispatched drill.
no findings · tests not needed · risk high

The only files changed since the last review are two docs pages recording the new PlanetScale OIDC trusts; no workflow or code changed. Nothing to review, and everything the docs claim matches the workflows at the head.

Before merge

  • Env var · Add PLANETSCALE_OIDC_TRUST_ID to the repository's CI variables · .github/workflows/backup-restore-test.yml:68
  • Manual · Watch the first deploy-prd.yml run for us and eu, then dispatch backup-restore-test.yml
  • Manual · After both are green, delete PLANETSCALE_API_TOKEN_ID / PLANETSCALE_API_TOKEN from Infisical prod and prod-eu and revoke alchemy-deploy
What was checked
  • Infisical export-type: env (deploy-setup/action.yml:54) puts PLANETSCALE_ORGANIZATION in env before the auth step
  • deploy-prd.yml:21 grants id-token: write to the reusable deploy
  • environment: production/production-eu is set only by deploy-prd-instance.yml:24, so the docs' trust scope holds

f4bd8e8 · Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.