OOB Deploy Request

[GcioNapoleon]

Instructions

Please fill out the necessary details and list the PRs related to the OOB deployment in the sections below.

PRs Related to OOB

• Please provide the list of PRs related to the need for this OOB Deploy below:

  Revert-VFEP-1502

Active Daily Users Impacted

• How many active users are impacted at this time and day.

  All Users who try and use 1990 form

  Has fix been confirmed in Staging?

• [x] Yes
• [ ] No

Description

• Please provide the details/reason for the OOB Deploy

  We merged the change 2 minutes before the cutoff and it was not picked up by the daily deployment process. Code was push to prod for form 22-1990 that should not be in prod. This code change is derived from a verdict of the Rudisill v. McDonough case. The code should not be in production and needs to be removed. Staging has the reverted code.

Verify The following

• [x] The OOB Deploy Request is after the 2pm EST cutoff for regular deploy.[^1]
• [x] The OOB Deploy Request is critical and must be resolved before the next automated deploy.
• [x] You are prepared to create an Incident Post Mortem^2 within two business days.

[^1]: (See Deployment Policy and Deployment Schedules

Performed by Platform Support Team

• [x] PagerDuty OOB Deploy Incident Opened
• [x] OCTO-DE staff acknowledgment of Request, via /pd trigger
• [x] Notification is posted in the appropriate Slack support and team Channels
• [x] Infrastructure/Operations has acknowledge the Requests

• [x] Security Team has Reviewed the requests

  CC: @department-of-veterans-affairs/vsp-operations , @department-of-veterans-affairs/vsp-product-support

[bdech]

Support request for OoB https://dsva.slack.com/archives/CBU0KDSB1/p1719350302644369

[va-vsp-bot]

This issue is stale. If it is no longer valid, please close issue. Otherwise please update