registry_upload.yml

name: Create and publish a Docker image

# Configures this workflow to run on main when testing CI is completed.
on:
  push:
    tags:
      - "*"

# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}
  CPU: "arm64"

jobs:
  on-failure:
    runs-on: ubuntu-latest
    if: ${{ github.event.workflow_run.conclusion == 'failure' }}
    steps:
      - run: echo 'The triggering CI workflow failed'
  docker-build-and-publish:
    runs-on: ubuntu-latest
    if: ${{ github.event.workflow_run.conclusion == 'success' }}
    # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
    permissions:
      contents: read
      packages: write
    strategy:
      matrix:
        include:
          - context: ./datastore/datastore/
            IMAGE_NAME: datastore
          - context: ./api/
            IMAGE_NAME: api
          - context: ./ingest/
            IMAGE_NAME: ingest
          - context: ./datastore/migrate/
            IMAGE_NAME: migrate
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v3
        with:
          platforms: ${{ env.CPU }}

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      # Uses the `docker/login-action` action to log in to the Container registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
      - name: Log in to the Container registry
        uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
      - name: Extract metadata (tags, labels) for Docker
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY }}/${{ github.repository }}/${{ matrix.IMAGE_NAME }}
          # Flavor auto will autmaticlly add the latest tag to the most recent image
          flavor: |
            latest=auto
          # type=ref will create custom tags, from whatever branch/tag that is created
          # type=pep440 will only run on main branch, when there is a semantic tag added to a commit.
          # pep440 is same as semver but also accept tags without the v in front.
          tags: |
            type=ref,event=tag,enable={{!is_default_branch}}
            type=pep440,pattern={{version}},enable={{is_default_branch}}

      - name: Install just
        run: ./ci/scripts/install-just.sh

      - name: Copy Protobuf files to Dockerfile directories
        run: just copy-proto

      # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
      # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
      # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
      - name: Build and push Docker image
        uses: docker/build-push-action@v5
        with:
          context: ${{ matrix.context }}
          platforms: linux/arm64, linux/amd64
          file: ${{ matrix.context }}/Dockerfile
          pull: true
          push: true
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}