Instructions

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

PRs Related to OOB

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

Unknown, but this is likely not a heavily trafficked page.

[x] Yes, @hgbarreto confirmed the fix worked in a staging and prod preview deploy of my PR / branch
[ ] No

Please provide the details/reason for the OOB Deploy

I merged some redirects yesterday and immediately after merged another set of redirects. I did not notice, when merging the second set of redirects, that I had inadvertently removed the matcher from the very last redirect in the first batch. It caused the source and destination values of the redirect to work backwards.

[ ] 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.

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 (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