Deployment Process

1. Create a PR for your change in this repository.
2. Once approved, this will push changes to the Gitops repo here: https://github.com/[bcgov-c/tenant-gitops-dc0a4a](https://github.com/bcgov-c/tenant-gitops-dc0a4a)
3. Argo will see the changes and deploy to Emerald.
4. There are 5 slots available in the development environment that can be deployed to. These slots are referred to as dev-1, dev-2, ..., dev-5. In order to determine which slot will be used the pipeline will use your PR# and perform the following calculation:
   • (PR# mod 5) + 1
   • Example 1: if your PR number is 30: (30 mod 5) + 1 = 0 + 1 = dev-1
   • Example 2: if your PR number is 98: (98 mod 5) + 1 = 3 + 1 = dev-4
5. In order to mitigate slot conflicts (for example: if PR 30 and PR 35 are both active at the same time) all deployments to the dev environment must be manually approved. A migration to dev should not be approved if an open PR is already occupying the slot.

Note that in the diagram below, images are automatically copied over from GHCR to Artifactory. This needs to be done because Github doesn't have a route to the Emerald Cluster, so we can't push images there directly. Emerald does have access to Artifactory though.