Names: May 5th Bug Release

[jmills-cgi]

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

• Update version number in the code being released
• Ensure deployment steps are filled in - remove/replace placeholders
• Create a draft release in GitHub and confirm the correct commits are present
• Add version # and release # to this ticket 2.1.2
• QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
• Dev/QA chat to plan prod verification testing (unless already automated)
• Release the code to production and complete smoke test (STEPS BELOW)
• Finalise/publish the release in GitHub, tagging it

Deployment Steps

Dev:

• config map changes
  • none
• deployments
  • namex-pay
  • namex-api
  • namerequest
• are there any one-time scripts to be run, such as for data migration?
  • none

Test:

• config map changes
  • none
• deployments
  • namex-pay
  • namex-api
  • namerequest
• are there any one-time scripts to be run, such as for data migration?
  • none

Prod:

• config map changes
  • none
• deployments
  • namex-pay
  • namex-api
  • namerequest
• are there any one-time scripts to be run, such as for data migration?
  • none

Smoke Test Script

• watch Kibana logs for 5 minutes