Harvest2.0 Platform Released in staging and production

[jbrown-xentity]

User Story

In order to prepare H2.0 for production, data.gov admins want Harvest2.0 systems setup in cloud.gov staging and production.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN we have a set of apps and services for harvester 2.0
  AND we have determined that most of the development churn has stabilized
  AND we have created a series of steps necessary to recreate a new environment
  THEN we want to perform those in the staging environment, confirm that those steps are correct, then proceed to perform those steps in production

• GIVEN a stable release is ready for merging via PR
  WHEN a PR to main happens
  THEN the changes are deployed to staging (with smoke test) and then onto production.

Background

Needed before we do complete load test and cutover: #4964

Security Considerations (required)

None

Sketch

Most of the automation is commented out, this was only done to keep resources low and costs down. This should be doable, but first deployment might come with some bugs.
A check before and after staging deployment should be conducted to see how much memory this is taking in practice, and if we need to do any scaling and/or if production is safe to release.