OOB Deploy Request

[eselkin]

DevOps repo, forward proxy deploy OOB request

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:

  https://github.com/department-of-veterans-affairs/devops/pull/14572

Active Daily Users Impacted

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

  Between 150 to 500 requests per day, so 3 days of no requests is approximately at max 1500 users. Below is requests over one week, leading up to Friday Aug 2, on the facilities_api/v2/va/ccp endpoint.

  

Has fix been confirmed in Staging?

• [ ] Yes
• [x] No - but testing was done on the endpoint to make sure it

Description

• Please provide the details/reason for the OOB Deploy

  vets-api will deploy at 1pm EST pulling in a new key for the new endpoint in the forward proxy. If the forward proxy does not deploy

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

• [ ] Security Team has Reviewed the requests

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

[ph-One]

New and old URLs return the same values. LGTM

[ph-One]

http://jenkins.vfs.va.gov/job/deploys/job/fwdproxy-vagov-prod/1266/