Closed ian-sears closed 2 weeks ago
@omahane Clarity. This was one of my first Facility GH tickets back in March. I may have created this entirely wrong. Facility Status: This came in via prod Flagged Facilities as Removed From Source. (still has this Flag) In short, Elmendorf-Richardson VA Clinic (vha_463QA) has Closed (as per the Editor) it is being REPLACED by Joint Base Elmendorf VA Clinic (vha_463A4) in Draft, not in CSV, Editor needs to fill out <- I'm on it .
So, I think? the strategy shoul dbe to Bring the New Joint Base facility online. Then, move the url traffic.
I'll rewrite these GH tickets to be correct now that I better understand our process.
CLosing based on notes in https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17658
@ian-sears I'd love to wait on this until the replacement facility is ready to be published. Do we have any idea about when that might be?
@omahane New Facility Join Base Elmendorf complete. Published. Soon as you get #18489 LH Canonical to resolve we can continue on with this vha_463QA redirect to vha_463A4,https://www.va.gov/alaska-health-care/locations/joint-base-elmendorf-richardson-va-medical-center/
The redirect request has been made: https://github.com/department-of-veterans-affairs/vsp-platform-revproxy/pull/535
Redirect has deployed. Waiting for vha_463QA | https://www.va.gov/alaska-health-care/locations/elmendorf-richardson-va-clinic to be removed from the CSV. @omahane fysa
Per flagged facilities sync:
https://www.va.gov/find-locations/facility/vha_463QA is removed This is ready for CSV update in Lighthouse. FYI @omahane
Page can now be archived, since the redirect is live. FYI @ian-sears
The URL removal request has been made: https://dsva.slack.com/archives/C02BTJTDFTN/p1724077493106109
Implementation date
When does this request need to be live: Pending Editor response
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.)
ansible/deployment/config/revproxy-vagov/vars/redirects.yml
URL Redirect
Use one of the following:
2. Canonical URL removal (if removed from VAST)
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 removal
URL removal example (update with actual ID and URL to remove)