Skip to content

ci: use repository variables for shared CI/CD config - #131

Open
sukhada wants to merge 1 commit into
mainfrom
chore/use-repo-variables
Open

ci: use repository variables for shared CI/CD config#131
sukhada wants to merge 1 commit into
mainfrom
chore/use-repo-variables

Conversation

@sukhada

@sukhada sukhada commented Mar 21, 2026

Copy link
Copy Markdown

Summary

Replaces the hardcoded env block in ci-cd.yml with repository variables (vars.*). This eliminates duplication across workflow files — the seed-staging workflow (#130) and any future workflows can reference the same variables without copying values.

Before

env:
  GCP_REGION: us-west1
  WIF_PROVIDER: projects/630731592917/...
  # ... 6 more hardcoded values

After

env:
  GCP_REGION: ${{ vars.GCP_REGION }}
  WIF_PROVIDER: ${{ vars.WIF_PROVIDER }}
  # ... references to repository variables

Prerequisites

Most repository variables are already required by #130. The only new variable this PR needs:

Variable Value
GAR_REGISTRY us-west1-docker.pkg.dev/spoke-407503/spoke/core

All other variables (GCP_REGION, GKE_CLUSTER, GKE_LOCATION, STAGING_NAMESPACE, STAGING_DEPLOYMENT, WIF_PROVIDER, WIF_SERVICE_ACCOUNT) are already listed as prerequisites in #130.

Test plan

  • Add GAR_REGISTRY repository variable in GitHub Settings → Variables → Actions
  • Merge and verify CI pipeline passes (test + deploy-staging on main, publish-docker-image on tag)

🤖 Generated with Claude Code

Replace hardcoded env values in ci-cd.yml with repository variables
(vars.*). This allows the same values to be shared across multiple
workflow files without duplication and drift.

Repository variables to set in GitHub Settings → Variables:
  GCP_REGION, GAR_REGISTRY, GKE_CLUSTER, GKE_LOCATION,
  STAGING_NAMESPACE, STAGING_DEPLOYMENT, WIF_PROVIDER,
  WIF_SERVICE_ACCOUNT

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

1 participant