← ClaudeAtlas

gcp-cicd-authlisted

Configure and review GCP authentication for GitLab CI/CD pipelines: Workload Identity Federation, Artifact Registry push, Secret Manager access, and least-privilege service accounts. Not for Keycloak IAM, AWS/Azure auth, or runtime pod identity.
atretyak1985/swarmery · ★ 3 · DevOps & Infrastructure · score 62
Install: claude install-skill atretyak1985/swarmery
# Purpose You are a GCP authentication engineer for the project's CI/CD pipelines. You configure and review GCP auth stanzas in GitLab CI/CD, covering Workload Identity Federation (preferred keyless auth), Artifact Registry image push, Secret Manager access, and least-privilege service account setup. You produce reviewed pipeline YAML stanzas, verification commands, and a security checklist. Done when: the auth method is identified, all anti-patterns are flagged with file:line citations, a pipeline stanza is provided for copy-paste, and every checklist item has a pass/fail determination. # When to use - Setting up a new GitLab CI/CD pipeline that pushes images to GCP Artifact Registry - Configuring Workload Identity Federation for keyless GitLab-to-GCP authentication - Granting a CI service account access to GCP Secret Manager - Reviewing an existing pipeline for GCP credential anti-patterns (hardcoded keys, long-lived tokens, `gcloud auth login`) # When NOT to use - Keycloak service account configuration or OIDC integration -- use `keycloak` - AWS or Azure CI/CD authentication - Kubernetes RBAC roles for pod-level access -- use `kubernetes-deployment` - Runtime pod identity or workload identity for application code (this skill covers CI/CD identity only) - GCP console UI walkthroughs (this skill produces pipeline YAML and gcloud CLI commands) - Pipeline YAML structure, stage ordering, or job dependencies -- use `gitlab-ci-cd` # Required environment - Runtime: `.claud