OOB Deploy Request

[eselkin]

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 "VACMS 12908 LH v0 to v1 nearby va locations VAMC, VBA, Vet Center (#29890)" vets-website#30032

Active Daily Users Impacted

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

Has fix been confirmed in Staging?

• Yes
• No (but it is all the changes that started causing the errors)

Description

• Please provide the details/reason for the OOB Deploy

  Requests to the new Facilities API v2 vets-api endpoint (facilities_api/v2/va) resulted in 403s because the POST request requires a api_session token set in cookies that is not available on first request.

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
• Security Team has Reviewed the requests

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 ↩

[va-vsp-bot]

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