-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release Staging Workflow Updates for Helm #491
Comments
Sync up with Ben and decide on how to accomplish. this without everyrthing exploding |
Managed to make some progress with this code so the credentials are starting to work, but not completely. will work with Ben on this today |
Workflows added for Admin and Manifests! It runs and updates accordingly. Need to add them to the other 3 components, next... to be continued. PRs: |
Should be able to get this finished today :fingers_crossed: |
Doc D, Documentation, API and Admin have all been updated accordingly, and they are all working as they should! I've verified all of the tags, and they match what's in our Public ECR. I've also added the secrets to Terraform that are required for our PR Dispatches to work (ie. API Repo Workflow Calls --> Manifests Repo Workflow). PRs are all listed above! That is all :) |
There was an issue in the code where it still wasn't picking up the image versions and was defaulting to latest. That was corrected yesterday. Will verify today. |
Ben will finish QAing today |
Looks good! |
Description
As a developer I'd like our code and release automation to have parity between Staging and Production so that there are no discrepancies when debugging or releasing code.
WHY are we building?
Our current process doesn't have parity between these environments, and with updates being made due to our helmfile rollout, we have to make these changes to account for the update. The main goal here is to clean up how our docker images are tagged for our 4 notify components (admin, api, doc download and documentation)
WHAT are we building?
updated workflows so that both staging and production use the same image tags and basic release process in manifests to update it's version/code. ADR below outlines the principal:
https://github.com/cds-snc/ADR/blob/d45e79b604ea471b4b05365ffb31d2a04a11f0e7/0015_GC_Notify_Release_Automation.md
VALUE created by our solution
Much simpler and easy to understand release process and parity between environments which we should strive to have.
Acceptance Criteria
QA Steps
The text was updated successfully, but these errors were encountered: