Google Cloud Platform

GCP is used by Just About for building, logging & hosting of jarb, the next version of the Just About API.

We primarily use the following products:

• Cloud Storage: Manages storing build artifacts for use in compilation of a docker image
• Cloud Build: Manages building docker images & storing the resulting artifacts in Artifact Registry
• Cloud Artifact Registry: Stores & manages versions of docker images
• Cloud Run: Hosts docker images in containers, manages auto-scaling
• Cloud Secrets Management: Stores secrets which are injected into Cloud Run containers

We have two projects, production and staging:

• Production: prod-just-about-76261c76
• Staging: staging-just-about-b6587c00

---

JARB is automatically deployed to GCP via our in-house action, deploy-cloud-run which can be found at .github/actions/deploy-cloud-run.

This action is used to deploy both production & staging:

• Production: https://github.com/Just-about/just-about/blob/167945845174d5f202a78aa65b41b2f24de7d096/.github/workflows/deploy-production.yaml#L125-L168
• Staging: https://github.com/Just-about/just-about/blob/167945845174d5f202a78aa65b41b2f24de7d096/.github/workflows/deploy-staging.yaml#L100-L142

Here's a short overview of how it works:

• 1. Developer makes a commit to a PR / dev branch, the deploy-cloud-run composite action is invoked as part of the workflow
• 2. The workflow collects all files listed within the image-sources, packaging them into an archive & pushing it to Cloud Storage
• 3. A Cloud Build request is submitted taking the Dockerfile.jarb and creating an image, which is then stored in Artifact Registry
• 4. Depending on if a Cloud Run service already exists with the name gcp-cloud-run-service-name, the workflow with either update the service with the newly created image, or create a service from scratch