Procedure for updating the SQuaSH production instance

Lets use the branch tickets/DM-12345 as and example and pretend that the change is in the squash-bokeh micro service

1) After implementing a new feature and testing it locally, push all changes to the ticket branch

cd squash-demo/squash-deployment/squash-bokeh
git push origin tickets/DM-12345

2) Exercise the deployment on the squash-demo instance

Set the kubectl context and deployment namespace to demo

cd squash-demo/squash-deployment/
NAMESPACE=demo make switch-namespace

2.1) Make sure the change works with the current production database

Clone the squash-db-prod Cloud SQL instance to a new squash-db-demo instance

Delete the previous squash-db-demo Cloud SQL instance

2.2) Build a new docker image for the squash-bokeh micro service

cd squash-bokeh/
TAG=DM-12345 make build push

Make a new deployment for the squash-bokeh service

TAG=DM-12345 make deployment

2.3) Test the results at https://squash-demo.lsst.codes

2.4) Assuming everything work as expected and travis tests passes you can merge the change to master.

3) Make a new deployment of the squash-bokeh micro service to the production instance

3.1) Set the kubectl context and the deployment namespace to squash-prod

cd squash-prod/squash-deployment/
NAMESPACE=squash-prod make switch-namespace

3.1) Update your local master branch and build a new docker image for the squash-bokeh micro service

cd squash-bokeh/
git pull
TAG=latest make build push

3.2) deploy to production

TAG=latest make deployment