Setup Google Cloud Run for Backend Deployment

This skill creates the necessary Google Cloud resources for deploying the backend to Cloud Run, and optionally updates GitHub Actions workflows to use the new resource names.

Instructions

You are setting up Google Cloud Run infrastructure for the backend deployment. Follow these steps carefully:

Step 1: Gather Information

Ask the user for the new app name using AskUserQuestion. This name will be used to derive:

• •Artifact Registry repository name: the app name in lowercase, kebab-case (e.g., my-app)
• •Cloud Run service name: the app name with -api suffix (e.g., my-app-api)
• •GCP region: default to australia-southeast1 but ask if they want a different region

Present the derived names and ask for confirmation before proceeding.

Step 2: Verify Prerequisites

Run these checks and report results to the user:

gcloud auth list --filter=status:ACTIVE --format="value(account)"
gcloud config get-value project

If no active account or project, tell the user to run gcloud auth login and gcloud config set project PROJECT_ID first, then re-run this skill.

Step 3: Enable Required APIs

Run these commands (they are idempotent):

gcloud services enable cloudbuild.googleapis.com
gcloud services enable run.googleapis.com
gcloud services enable artifactregistry.googleapis.com

Step 4: Create Artifact Registry Repository

Check if the repository already exists first:

gcloud artifacts repositories describe REPO_NAME --location=REGION 2>/dev/null

If it doesn't exist, create it:

gcloud artifacts repositories create REPO_NAME \
  --repository-format=docker \
  --location=REGION \
  --description="Docker images for APP_NAME backend"

If it already exists, inform the user and skip creation.

Step 5: Deploy Initial Cloud Run Service

Deploy a minimal Cloud Run service to establish it. Use the backend Dockerfile:

cd backend
gcloud run deploy SERVICE_NAME \
  --source . \
  --region REGION \
  --allow-unauthenticated \
  --set-env-vars "GIN_MODE=release" \
  --set-env-vars "TIMEZONE=Australia/Sydney"

After deployment, retrieve and display the service URL:

gcloud run services describe SERVICE_NAME \
  --region REGION \
  --format 'value(status.url)'

Step 6: Ask About GitHub Actions Update

Ask the user (using AskUserQuestion) whether to update the GitHub Actions workflows to use the new resource names. The options should be:

1. •Yes, update all workflows - Updates deploy.yml, preview-deploy.yml, and preview-cleanup.yml
2. •No, skip workflow updates - Only the GCP resources were created

Step 7: Update GitHub Actions (if confirmed)

If the user confirmed, update the following files:

.github/workflows/deploy.yml:

• •ARTIFACT_REGISTRY_REPO env var → new repo name
• •BACKEND_SERVICE_NAME env var → new service name
• •SENDGRID_FROM_NAME → new app display name

.github/workflows/preview-deploy.yml:

• •ARTIFACT_REGISTRY_REPO env var → new repo name
• •BACKEND_SERVICE_NAME env var → new service name
• •SENDGRID_FROM_NAME → new app display name

.github/workflows/preview-cleanup.yml:

• •The hardcoded service name in the gcloud run services update-traffic command → new service name

Step 8: Report GitHub Secrets to Verify

After all changes, inform the user about the GitHub repository secrets they should verify/update. List them in a clear table format:

Highlight which secrets are most likely to need updating based on whether a rebrand or project migration is happening.

Important Notes

• •Always show the user what commands will be run BEFORE executing them.
• •If any GCP command fails, show the error and suggest troubleshooting steps.
• •Do NOT modify any secrets or environment variables in Cloud Run beyond the initial deploy — those are managed via GitHub Actions secrets.
• •The initial Cloud Run deploy in Step 5 may take a few minutes. Warn the user about this.