CD Pipeline - Deploy to Production

[ldraney]

User Story - Business Need

This ticket is the final stage to completing our CD Pipeline according to this diagram.

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As VA Notify <!--- describe the affected user --->
I want Continually deploy production-ready code <!--- describe the need --->
So that application upgrades and features are made available to clients as soon as possible, and engineer hours managing this process are significantly reduced <!--- describe the outcome] --->

Additional Info and Resources

cd-pipeline.yml already has various stops for QA; This is the final run merge and run through of this pipeline.

Engineering Checklist

• Add to the cd-pipeline.yml, after the final check of QA for the prod-deploy environment, a workflow_call to dev_deploy.yml for the prod environment.
• Run through workflow with QA after merging this PR, ensuring all looks correct.

Acceptance Criteria

• After QA approval, Github Actions deploys the new version to production and runs the Prod smoke test

QA Considerations

• work with the dev to ensure that the work done in this ticket meets the necessary requirements

Out of Scope

• Publishing the drafted release notes is in #1721

[npmartin-oddball]

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @k-macmillan @kalbfled @ldraney @MackHalliday @mchlwellman

[ldraney]

I've contacted Cris and we will be syncing on this after standup.

[ldraney]

Things are looking good, but I would like to continue work on Monday after I figure out my E-Pass stuff today. This is a high priority because it may expire Monday!
Also, we like to avoid deploying on Fridays. I've passed this by Cris and Kyle. I will wait until Monday morning to sync with Cris before creating a PR.

Here’s what I’ve accomplished on the ticket so far.
I got a working POC.
Here is the PR in demo api of the code I merged.
I also discovered the cd-pipeline wasn't passing the tag to deploy-release.yml, so I included the fix in the above PR and wrote out these notes about the fix.

I’ve also written out some steps for a smooth transition to the new pipeline, and tested it in my POC to make this release.

[ldraney]

Epass looking good! Getting back to this.

[ldraney]

Had a sync with Cris and things look good!
We need to make sure in standup the team is okay with an out of cycle release, and to move forward with this process.
Then I'll open a draft PR!