gcp-deployment

스타10

포크2

업데이트2026년 5월 24일 09:39

Deep knowledge about deploying applications to Google Cloud Platform (Cloud Run, App Engine, Compute Engine).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

porcupine-md

porcupine-md/jonggrang

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Context

Deploying {{project_name}} ({{project_type}}) to Google Cloud Platform (GCP). You will follow a strict 6-phase Deployment Lifecycle Contract.

Instructions

Execute the following phases in order:

Phase 1: Authentication

Ensure the GOOGLE_APPLICATION_CREDENTIALS environment variable is set to a valid service account key JSON file, or configure Workload Identity Federation (if inside CI/CD).
Authenticate the gcloud CLI: gcloud auth activate-service-account --key-file=$GOOGLE_APPLICATION_CREDENTIALS.
Set the default project: gcloud config set project <PROJECT_ID>.

Phase 2: Build

Prepare the artifacts for deployment.
If Cloud Run or GKE: build your Docker image (e.g., docker build -t gcr.io/<PROJECT_ID>/<APP_NAME> . or gcloud builds submit --tag gcr.io/<PROJECT_ID>/<APP_NAME>).
If App Engine: prepare app.yaml.
If Static Site (Cloud Storage): run npm run build.

Phase 3: Install / Provisioning

Ensure the target GCP resources (Cloud Run services, Buckets, Compute Instances) exist and you have permissions to write to them.
If Cloud Storage: gsutil ls gs://<bucket-name>.
Enable necessary APIs (e.g., gcloud services enable run.googleapis.com if using Cloud Run).

Phase 4: Deploy

Ship the artifact to GCP.
Cloud Run: gcloud run deploy <SERVICE_NAME> --image gcr.io/<PROJECT_ID>/<APP_NAME> --region <REGION> --platform managed.
App Engine: gcloud app deploy.
Cloud Storage: gsutil rsync -R dist/ gs://<bucket-name>.

Phase 5: Checking

Verify the deployment was successful.
Cloud Run: Check the returned service URL via curl and inspect gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>" if it fails.
App Engine: Check the target URL.
Ensure the service returns HTTP 200.

Phase 6: Update / Rollback

If Phase 5 fails, immediately initiate a rollback.
Cloud Run: Route 100% of traffic to the previous revision (gcloud run services update-traffic <SERVICE_NAME> --to-revisions=<PREVIOUS_REVISION_NAME>=100 --region <REGION>).
App Engine: Roll back traffic to an older version via gcloud app services set-traffic.
Note the failure in the progress log.

Validation

GCP authentication succeeds.
Build succeeds.
Artifacts are deployed.
Health check (curl) returns 200 OK.

이 저장소의 다른 Skills

같은 저장소

jonggrang

porcupine-md/jonggrang

Deterministic AI development workflow orchestrator. Manages task boards (.jonggrang/jonggrang-tasks.json), runs 16-phase pipelines (BUGFIX/SMALL/MEDIUM/LARGE), installs lifecycle hooks for Claude Code and OpenCode, and coordinates five specialist roles (Lead/Developer/Reviewer/TestLead/Tester). Use when planning features, executing multi-step development workflows, or orchestrating AI coding agents. Run via npx jonggrang.

2026-07-2910

orchestrating-feature

porcupine-md/jonggrang

16-phase feature orchestration workflow. Runs in the main thread as Kernel Mode. Coordinates the Lead→Developer→Reviewer→TestLead→Tester assembly line.

2026-06-2310

persisting-agent-outputs

porcupine-md/jonggrang

Protocol for agents to write structured outputs that survive session resets and are findable by the orchestrator.

2026-06-1310

porcupine-md/jonggrang

GitHub workflow automation with the gh CLI — pull requests, issues, releases, the REST/GraphQL API, and safe message escaping. Auth via GH_TOKEN (set in global settings, attached to the sandbox env).

2026-06-0810

glab

porcupine-md/jonggrang

GitLab workflow automation with the glab CLI — merge requests, issues, CI, releases, and safe message escaping. Auth via GITLAB_TOKEN (set in global settings, attached to the sandbox env).

2026-06-0810

iterating-to-completion

porcupine-md/jonggrang

Prevents premature exit and infinite loops. Three mechanisms: Completion Promises, Scratchpads, Loop Detection.

2026-05-2410

name	gcp-deployment
description	Deep knowledge about deploying applications to Google Cloud Platform (Cloud Run, App Engine, Compute Engine).
type	transform
tier	library
domain	deploy
trigger	when deploying to GCP

Context

Deploying {{project_name}} ({{project_type}}) to Google Cloud Platform (GCP). You will follow a strict 6-phase Deployment Lifecycle Contract.

Instructions

Execute the following phases in order:

Phase 1: Authentication

Ensure the GOOGLE_APPLICATION_CREDENTIALS environment variable is set to a valid service account key JSON file, or configure Workload Identity Federation (if inside CI/CD).
Authenticate the gcloud CLI: gcloud auth activate-service-account --key-file=$GOOGLE_APPLICATION_CREDENTIALS.
Set the default project: gcloud config set project <PROJECT_ID>.

Phase 2: Build

Prepare the artifacts for deployment.
If Cloud Run or GKE: build your Docker image (e.g., docker build -t gcr.io/<PROJECT_ID>/<APP_NAME> . or gcloud builds submit --tag gcr.io/<PROJECT_ID>/<APP_NAME>).
If App Engine: prepare app.yaml.
If Static Site (Cloud Storage): run npm run build.

Phase 3: Install / Provisioning

Ensure the target GCP resources (Cloud Run services, Buckets, Compute Instances) exist and you have permissions to write to them.
If Cloud Storage: gsutil ls gs://<bucket-name>.
Enable necessary APIs (e.g., gcloud services enable run.googleapis.com if using Cloud Run).

Phase 4: Deploy

Ship the artifact to GCP.
Cloud Run: gcloud run deploy <SERVICE_NAME> --image gcr.io/<PROJECT_ID>/<APP_NAME> --region <REGION> --platform managed.
App Engine: gcloud app deploy.
Cloud Storage: gsutil rsync -R dist/ gs://<bucket-name>.

Phase 5: Checking

Verify the deployment was successful.
Cloud Run: Check the returned service URL via curl and inspect gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>" if it fails.
App Engine: Check the target URL.
Ensure the service returns HTTP 200.

Phase 6: Update / Rollback

If Phase 5 fails, immediately initiate a rollback.
Cloud Run: Route 100% of traffic to the previous revision (gcloud run services update-traffic <SERVICE_NAME> --to-revisions=<PREVIOUS_REVISION_NAME>=100 --region <REGION>).
App Engine: Roll back traffic to an older version via gcloud app services set-traffic.
Note the failure in the progress log.

Validation

GCP authentication succeeds.
Build succeeds.
Artifacts are deployed.
Health check (curl) returns 200 OK.