CMP Deployment Checklist

Do you have everything you need in place?

• All properties.yml files in root/manifests/environments with the secrets file and root URL correct for the environment
• gunicorn.conf.py (see CMP documentation about configuration)

Is this a first-time deployment in CMP from PyPE? If so, leave the application running in PyPE.

Things to do

For a first-time deployment to an environment (DEV/QUAL/PROD) and/or namespace (Staging/Production), it's expected that the deployment won't work correctly after the first deployment, because of automagic processes pulling secrets from Rancher in with the project. Be ready for multiple deployments to fix this.

1. Deploy the branch of your choice to the environment of your choice with the Actions tab in github, under Build and Deployment, and select Run workflow
   1. If it's production, you'll need to verify the deployment. This is a setting in github. It can be turned off.
2. When that's complete, cllick on Deployment Results and let that finish. This takes about 5 minutes in all.
3. Deployment results will show the stack trace and any errors, or tell you it was a successful deployment.
4. Now go to Rancher and look for the namespace and secrets. If the namespace was just created by an initial deployment, you'll likely have to shift + refresh to get it to appear in the browser.
5. Create your secrets (perhaps by cloning from a prior environment) and make sure they're in the right namespace (staging = DEV and QUAL) for the right project.
   1. Wrong namespace means UT Login tends to work, since those credentials work the same on all our projects, but then you get a failed connection to the (wrong) database
6. Redeploy the project in github to pull in the secrets. Then the deployment should work.
   1. Modifying secrets that already exist should be pulled in within a few moments.

If the project was running in PyPE, you can now stop the PyPE server for that environment and route to CMP from PyPE.