Release: 3rd Party Access - Request Access

[steveburtch]

Release Date and Time: Tue Dec 5, 9:00 AM
Release Contacts: HF (BTR), TS (Relationships)
Release Approver: Steve B, PO BTR
Release Comms: MS (BTR)
Release QA: GS (BTR)

What's Changed: v2.9.3

https://github.com/bcgov/sbc-auth/releases
New affiliation method added to Business Registry: Request access to manage a business

• 18522, 18525 - updates to REQUEST affiliation by @hfekete in #2642
• 18653, 18380 - Affiliation REQUEST - additional updates by @hfekete in #2645
• 18086 - Removing last option from affiliation modal. by @hfekete in #2593
• 17778 & 17788 - Org Admin/Coordinator for affiliation invitation updates by @hfekete in #2572
• 17998 - Add key to clear the form after reset (on hiting cancel button). by @hfekete in #2576
• 17777 - Remove 'business authorized' message by @hfekete in #2568
• 17776 - Soft delete support for accepted affiliation invitations by @ochiu in #2564
• 16911 - Status rows for incoming and outgoing Affiliation Requests (Affiliation Invitation) by @hfekete in #2388
• 16222, 16384 - Affiliation Invitation - Access Request - Authorization & Emails by @hfekete in #2424
• 16384 - update where affiliation invitation authorize/refuse emails are being sent to. by @hfekete in #2439
• 17328 - Adding some extra TC for documenting purposes for check_auth. by @hfekete in #2443
• 16309 - Add api endpoints for Affiliation Invitation - request type by @hfekete in #2408
• 16222 - syncing template names between API and mailer. by @hfekete in #2429
• 16222, 16384 - Affiliation Invitation - Access Request - Authorization & Emails by @hfekete in #2424
• 16228 - Adding endpoint for retrieving accounts affiliated filtered b… by @hfekete in #2379
• 16220 - Account Authorization request UI component by @hfekete in #2383

Release Date:

Tues Dec 5 2023

Release Report:

https://app.zenhub.com/workspaces/registries-benowner-644043015b6fa1002c69a9f4/reports/release?release=Z2lkOi8vcmFwdG9yL1JlbGVhc2UvOTc4MDE

Release Plan:

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

Pre-Deployment Steps

• OCM comms plan
• Add release # to this ticket
• Confirm Ops is ready
• Ensure deployment steps are filled in - remove/replace placeholders

Deployment Steps

• Release the code to production
• Create a draft release in GitHub and confirm the correct commits are present
• Confirm the correct commits are present
• Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
• Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
• Finalise/publish the release in GitHub, tagging it

Post-Deployment Steps

• Smoke test PROD UI
• Monitor Sentry logs on going
• Monitor GCP logs on going
• Change banner on legacy site
• Final comms to stakeholders
  ...