adding docker container push to google artifact registry #3
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# This workflow build and push a Docker container to Harbor and deploys it on Cloud Run when a commit is pushed to the "main" branch | |
# | |
# Overview: | |
# | |
# 1. Authenticate to Google Cloud | |
# 3. Build a docker container | |
# 4. Publish it to Harbor | |
# 5. Deploy it to Cloud Run | |
# | |
# To configure this workflow: | |
# | |
# 1. Ensure the required Google Cloud APIs are enabled: | |
# | |
# Cloud Run run.googleapis.com | |
# Artifact Registry artifactregistry.googleapis.com | |
# | |
# 2. Create and configure Workload Identity Federation for GitHub (https://github.com/google-github-actions/auth#setting-up-workload-identity-federation) | |
# | |
# 3. Ensure the required IAM permissions are granted | |
# | |
# Cloud Run | |
# roles/run.admin | |
# roles/iam.serviceAccountUser (to act as the Cloud Run runtime service account) | |
# | |
# Artifact Registry | |
# roles/artifactregistry.admin (project or repository level) | |
# | |
# NOTE: You should always follow the principle of least privilege when assigning IAM roles | |
# | |
# 4. Create GitHub secrets for WIF_PROVIDER and WIF_SERVICE_ACCOUNT | |
# | |
# 5. Change the values for the GAR_LOCATION, SERVICE and REGION environment variables (below). | |
# | |
# NOTE: To use Google Container Registry instead, replace ${{ env.GAR_LOCATION }}-docker.pkg.dev with gcr.io | |
# | |
# For more support on how to run this workflow, please visit https://github.com/marketplace/actions/deploy-to-cloud-run | |
# | |
# Further reading: | |
# Cloud Run IAM permissions - https://cloud.google.com/run/docs/deploying | |
# Artifact Registry IAM permissions - https://cloud.google.com/artifact-registry/docs/access-control#roles | |
# Container Registry vs Artifact Registry - https://cloud.google.com/blog/products/application-development/understanding-artifact-registry-vs-container-registry | |
# Principle of least privilege - https://cloud.google.com/blog/products/identity-security/dont-get-pwned-practicing-the-principle-of-least-privilege | |
name: Docker Image CI | |
on: | |
push: | |
branches: [ "metocean-deploy-test" ] | |
pull_request: | |
branches: [ "metocean-deploy-test" ] | |
env: | |
PROJECT_ID: ${{ secrets.RUN_PROJECT }} # TODO: update Google Cloud project id | |
SERVICE: 'dgds-front-end-metocean' # TODO: update Cloud Run service name | |
REGION: ${{ secrets.RUN_REGION }} # TODO: update Cloud Run service region | |
jobs: | |
deploy: | |
# Add 'id-token' with the intended permissions for workload identity federation | |
permissions: | |
contents: 'read' | |
id-token: 'write' | |
runs-on: ubuntu-latest | |
steps: | |
- name: Checkout | |
uses: actions/checkout@v2 | |
# - name: Google Auth | |
# id: auth | |
# uses: 'google-github-actions/auth@v0' | |
# with: | |
# token_format: 'access_token' | |
# workload_identity_provider: '${{ secrets.WIF_PROVIDER }}' # e.g. - projects/123456789/locations/global/workloadIdentityPools/my-pool/providers/my-provider | |
# service_account: '${{ secrets.WIF_SERVICE_ACCOUNT }}' # e.g. - [email protected] | |
# NOTE: Alternative option - authentication via credentials json | |
- name: Google Auth | |
id: auth | |
uses: 'google-github-actions/auth@v0' | |
with: | |
credentials_json: '${{ secrets.GCP_CREDENTIALS }}' | |
- name: 'Build and Push Container' | |
run: |- | |
DOCKER_TAG="$${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/${{ env.SERVICE }}:latest" | |
docker build --tag "${DOCKER_TAG}" . | |
docker push "${DOCKER_TAG}" | |
# END - Docker auth and build | |
- name: Deploy to Cloud Run | |
id: deploy | |
uses: google-github-actions/deploy-cloudrun@v0 | |
with: | |
service: ${{ env.SERVICE }} | |
region: ${{ env.REGION }} | |
image: europe-west4-docker.pkg.dev/dgds-i1000482-002/dgds-metocean/dgds-front-end:latest | |
# If required, use the Cloud Run url output in later steps | |
- name: Show Output | |
run: echo ${{ steps.deploy.outputs.url }} |