Perform v0.12.0 Data Migration and Release

[jayfo]

Issue for tracking data migration and release of v0.12.0.

Steps to prepare for migration and release:

• Export pre-flight archives for:

  • [x] dev
  • [x] demo
  • [x] multicare
  • [x] scca

• Validate pre-flight archive to confirm pre-migration failure for:

  • [x] dev: Currently invalid, expected due to development documents. Not attempting to migrate.
  • [x] demo: No migration needed, none expected.
  • [x] multicare: No migration needed, none expected.
  • [x] scca: No migration needed, none expected.

• [x] Develop migration scripts:

  • [x] N/A

• Create release branch based on develop:

  • [x] release/v0.12.0

• [x] Ensure scope-aws-infrastructure Pipfile is using current release.

  • [x] N/A

• If migration required, validate migration script with migrated versions of pre-flight archives:

  • [x] dev: Not attempting to migrate.
  • [x] demo: No migration needed.
  • [x] multicare: No migration needed.
  • [x] scca: No migration needed.

• [x] Build images, requires updating version in 6 places:

  • docker/server_flask/codebuild_env.sh
  • docker/web_patient/codebuild_env.sh
  • docker/web_registry/codebuild_env.sh
  • tasks/codebuild/server_flask.py
  • tasks/codebuild/web_patient.py
  • tasks/codebuild/web_registry.py

Steps to execute migration and release:

• Freeze the database by stopping the associated server-flask, web-patient, web-registry services. This requires manually stoping each release with a helm uninstall command on the server (i.e., because the --skip-crds default in our Helmfile conflicts with installed).

  • [x] dev
  • [x] demo
  • [x] fredhutch and scca
  • [x] multicare

• Export final pre-migration archive:

  • [x] dev: Not attempting to migrate.
  • [x] demo
  • [x] multicare
  • [x] scca

• If migration not required, validate final pre-migration archive:

  • [x] dev: Not attempting to migrate.
  • [x] demo: No migration needed.
  • [x] multicare: No migration needed.
  • [x] scca: No migration needed.

• If migration required, apply and validate the migration.

  • [x] dev: Not attempting to migrate.
  • [x] demo: No migration needed.
  • [x] multicare: No migration needed.
  • [x] scca: No migration needed.

• If migration required, reset the database.

  • [x] dev: Not attempting to migrate.
  • [x] demo: No migration needed.
  • [x] scca: No migration needed.
  • [x] multicare: No migration needed.

• If migration required, restore the migrated archive.

  • [x] dev: Not attempting to migrate.
  • [x] demo: No migration needed.
  • [x] scca: No migration needed.
  • [x] multicare: No migration needed.

• Update Helmfile imageTag values for associated server-flask, web-patient, web-registry services.

  • [x] dev
  • [x] demo
  • [x] fredhutch and scca
  • [x] multicare

• Apply Helmfile to deploy release based on migrated data.

  • [x] dev
  • [x] demo
  • [x] fredhutch and scca
  • [x] multicare

Upload archives to Microsoft Teams.

• [x] dev
• [x] demo
• [x] scca
• [x] multicare

Document release deployments

• [x] Update v0.11.0 release data
• [x] Update v0.12.0 release data