OOB Deploy Request

[Thrillberg]

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:
  PR18752

Active Daily Users Impacted

• How many active users are impacted at this time and day.
  Unknown, our visibility/monitoring into all submissions of VFF forms has been zero since Sept. 27 and this fix will restore that

Has fix been confirmed in Staging?

• Yes
• No
  Staging has not deployed it but I did confirm that prior errors that were preventing this from working did not reproduce on local with this commit.

Description

• Please provide the details/reason for the OOB Deploy
  This commit will restore our monitoring in all VFF forms and will also fire off failure emails where appropriate.

Verify The following

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

Performed by Platform Support Team

• PagerDuty OOB Deploy Incident Opened
• OCTO-DE staff acknowledgment of Request, via /pd trigger
• Notification is posted in the appropriate Slack support and team Channels
• Infrastructure/Operations has acknowledge the Requests (This applies to revproxy and fwdproxy, but is not required for Frontend and Backend requests)
• Security Team has Reviewed the requests (This is not necessary for requests that are not related to security)

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

Footnotes

1. (See Deployment Policy and Deployment Schedules ↩

2. https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/tree/master/Postmortems ↩

[davidpetras]

OOB PD trigger skipped due to Matthew Dingee approval in Slack