URL Change for: Tulare VA Clinic to Visalia VA Clinic

[omahane]

Implementation date

When does this request need to be live: ASAP

Parent link: #18140

Instructions for URL redirect

(Note: This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.)

• [x] Notify VA stakeholders as appropriate.
• [x] Link the related facility closure / rename issue.
• [x] Create a URL redirect in the devops repo in ansible/deployment/config/revproxy-vagov/vars/redirects.yml
• [x] Add the "Awaiting redirect" flag to the facility node with a revision log message that includes a link to this ticket, preserving the node's current moderation state.
• [x] Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. After deploy, validate that the URL redirect is deployed. (Note: In the event of a facility closure or a name change, validate that this occurs before making the Lighthouse csv changes.)
• [x] Update this ticket with a comment that the redirect has been deployed.
• [x] Remove the "Awaiting redirect" flag on the facility node with a revision log message that includes a link to this ticket, preserving the node's current moderation state.
• [x] Notify helpdesk via comment on ticket or Slack message in #cms-support that changes are ready for review.

URL Redirect

Current URL	Redirect Destination or New URL
https://www.va.gov/central-california-health-care/locations/tulare-va-clinic	https://www.va.gov/central-california-health-care/locations/visalia-va-clinic

Use one of the following:

1. Canonical URL change

Note: Canonical URL changes do not block the completion of the parent ticket. Once the URL redirect above has been deployed, the value to the Veteran is delivered. This ticket should be kept open until the URL change is verified, except in the case of a removal (as described below).

Instructions for canonical URL change

• [x] Verify that the new URL for the facility is published and accessible on VA.gov.
• [x] Update the CSV in Lighthouse with the changed URL, maintaining the sorted order of the Facility API IDs.
• [x] Create a PR in the lighthouse-facilities repo, tagging the Lighthouse team.
• [x] Post a message in the #cms-lighthouse channel in Slack, with an @mention to a Lighthouse team member.
• [x] Add the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
• [x] Validate that the change has deployed by checking that the Facility Locator has been updated with the new url.
• [x] Update this ticket with a comment that the CSV change has been deployed.
• [x] Remove the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.

URL change example (update with actual ID and URL)

Facility API ID	Full VA.gov URL
vha_570GB	https://www.va.gov/central-california-health-care/locations/visalia-va-clinic

[TroyCMSSupport]

@omahane @jilladams @ian-sears - I believe this is ready to move forward

[ian-sears]

@omahane This redirect from Tulare to Visalia is not (yet) in lighthouse, not resolving (yet) to https://www.va.gov/central-california-health-care/locations/visalia-va-clinic

We can progress this facility's status once this older URL is redirecting.

Awaiting Redirect

[ian-sears]

Verified Redirect to Visalia is now in place. Awaiting CSV, now. CSV needs to be updated for Facility ID vha_570GB Please have it updated to https://www.va.gov/central-california-health-care/locations/visalia-va-clinic/ Awaiting CSV.

[ian-sears]

CSV has been updated. Resolving correctly in Facility locator. Closing as Completed.