Partner Team Quick Deployment Guide for Lower Environments
This guide outlines steps for VRO's partner teams to independently deploy and verify feature branch changes in dev and qa environments without the assistance of VRO engineers.
🚧 These instructions may evolve as VRO implements additional ArgoCD features. For example, on the VRO backlog is #3309, which has the potential for Slack integrations. 🚧
The commit may be on any branch that has been pushed to the public abd-vro repository. Copy the first 7 characters of the unique ID.
For a listing of commits on the
developbranch: Commits
Navigate to the configuration file specific for the app and environment(s):
- Contention Classification: dev.yaml, qa.yaml
- EP Merge: dev.yaml, qa.yaml
- Max CFI: dev.yaml, qa.yaml
- note: these are in private repository va-abd-rrd-argocd-applications-vault
Edit the file(s) so that image.tag is assigned to the value determined in Step 1. If imageTag is also defined, update its value, too. (Some configurations have both image.tag and imageTag; VRO is investigating whether the latter can be eliminated.) Commit the changes to a branch.
This example shows
image.tagandimageTagon lines 6 and 3, respectively:
Create a pull request (PR) for the branch.
Hold for the PR to be approved. Your team and the VRO team will automatically be notified of the pending PR (implemented through CODEOWNERS).
Merge the approved PR. ArgoCD will detect the change and execute the deployment as part of its auto-sync behavior. Its default polling interval: 3 minutes.
The deployment action will be visible on the Deployments by Image tag per Week tile of the VRO on LHDI dashboard. Use the "namespace" and "deployment" filters on the top bar to filter the results.
This screenshot shows the deployments for EP Merge on the dev and qa environments:
VRO is exploring options for pushing deployment status updates to Slack (#3309).
The below gif shows an example of creating a pull request for a deployment of domain-xample. Not shown: subsequent steps in GitHub and Datadog, as they are not unique to the deployment process.
