Update deployment doc after helm chart changes #218
Conversation
| 2. Commit a values YAML file in [values folder](https://github.com/medic/cht-user-management/blob/main/scripts/deploy/values/) in `main` branch | ||
| 3. Switch to the `deploy` branch and ensure the same values file from the prior step is in the [values folder](https://github.com/medic/cht-user-management/blob/deploy/scripts/deploy/values/) in `deploy` branch | ||
| 4. Edit the version in the `tag:` as the version you want deploy in the `helm` command below. Ensure this version in the `tag:` is commmited to `deploy` branch | ||
| 5. run either `helm install...` or `helm deploy...` per the full commands below. |
There was a problem hiding this comment.
Previously we wanted to use the deploy branch so that we didn't need to do a whole PR every time we wanted to push. I also think this might result in extra images being built and pushed to ECR? Slack thread:
For deployments, I've been pushing to this deploy branch which is probably lazy but I also don't want to make a new PR every time I push. And when I merge it, publishes duplicate images.
This changes that - but maybe it's OK because we want to not use deploy branch and over all are changing things less often?
There was a problem hiding this comment.
Previously we wanted to use the deploy branch so that we didn't need to do a whole PR every time we wanted to push....
Oh yes thats right, I got it and I think we still don't want to make a whole PR for every push, neither duplicated images published... :)
So maybe I should bring back the deploy branch use ? I am not sure I know the best thing to do here 😅
There was a problem hiding this comment.
I'd say let's revisit it in the #cht-user-management and we can discuss async.
Closes #217
Key points:
helm repo update).helm upgradeto work, delete existing helm values before reinstalling.