Entities Sprint 19.3a Release

[severinbeauvais]

Prior to moving into production, the following steps should be completed or confirmed:

• Add release # to this ticket
• Update version numbers in the code being released and list them here:
  • Business Create UI v5.5.7
  • Business Edit UI v4.7.4
  • Business Filings UI v6.9.4
  • Legal API v2.93.0
  • Entity Filer v2.93.0
  • Entity Emailer v2.93.0
• Ensure deployment steps are filled in - remove/replace placeholders
• Create a draft release in GitHub and confirm the correct commits are present

1. • Confirm the correct commits are present
2. • Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
3. • Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.

• Dev to ensure that the commit list is represented on the release report
• QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
• All dev/test pipeline test suites green
• Dev/QA chat to plan prod verification testing (unless already automated)
• Post message that projects are being deployed to Prod in #registries-entities
• Release the code to production and complete smoke test (STEPS BELOW)
• Post message that projects have been deployed to Prod in #registries-entities and #entities-ops
• Finalise/publish the release in GitHub, tagging it
• Merge release branch back to master (if applicable)
• Change openshift builds/pipelines back to master (if applicable)

Deployment Steps

Dev:

• Create UI v5.5.7 - done by CD script
• Edit UI v4.7.4 - done by CD script
• Filings UI v6.9.4 - done by CD script
• Legal API v2.93.0 - done by CD script
• Entity Filer v2.93.0 - done by CD script
• Entity Emailer v2.93.0 - done by CD script
  .
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook

Test:

• Create UI v5.5.7 - done by KJ on October 30
• Edit UI v4.7.4 - done by KJ on October 30
• Filings UI v6.9.4 - done by KJ on October 30
• Legal API v2.93.0 - done by AC on October 30
• Entity Filer v2.93.0 - done by KJ on October 30
• Entity Emailer v2.93.0 - done by KJ on October 30
  .
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook

Prod:

• Create UI v5.5.7 - done by KJ on November 7
• Edit UI v4.7.4 - done by KJ on November 7
• Filings UI v6.9.4 - done by KJ on November 7
• Legal API v2.93.0 - done by KJ on November 6
• Entity Filer v2.93.0 - done by KJ on November 6
• Entity Emailer v2.93.0 - done by KJ on November 6
  .
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook
  .
• notify the team via the #registries-ops channel

Smoke Test Script

• load Filings UI
• load Edit UI, eg, start change or alteration filing
• load Create UI, eg, start an IA or registration or voluntary dissolution
• watch Sentry logs for 60 minutes
• watch Kibana logs for 60 minutes