Deploying to Cloud Run with Pipery Cloud Run CD

Once a service is built and tested, the next question is how to deploy it without turning your workflow into another custom shell project. pipery-dev/pipery-cloudrun-cd gives you a reusable Cloud Run deployment step with the same observability story as the CI actions.

Minimal workflow#

name: CD

on:
  push:
    branches: [main]

jobs:
  cd:
    uses: pipery-dev/pipery-cloudrun-cd@v1
    with:
      image_name: ghcr.io/acme/api
      service_name: api
      region: europe-west1
      project_id: acme-platform-prod
    secrets: inherit

What the action does#

The deployment path is straightforward:

push the container image
deploy with gcloud run deploy
migrate traffic
run a status check

Inputs to care about early#

image_name: the image being deployed
image_tag: defaults to the current Git SHA, which is a sensible starting point
service_name: the Cloud Run service to update
region and project_id: define the deployment target
traffic: useful when you want a more careful rollout

Why teams like this pattern#

Cloud Run deployment is simple enough to start casually and tricky enough to drift over time. One team adds traffic handling, another adds status checks, another copies an old auth pattern. A shared action gives you the same deployment shape everywhere, and Pipery’s psh logs make post-deploy debugging much calmer when a rollout does not behave the way you expected.

Source and docs: pipery-cloudrun-cd.