Closed stefaniefgray closed 2 months ago
@omahane @ian-sears - Market Commons is ready for redirect
@omahane @jilladams @ian-sears - I believe the item still needs to be removed from the CSV (line number 934) Is this a step that Helpdesk can / should perform?
This archived location is 404ing in VA.gov, and that's not great. We should take action on this one - pulling into sprint 8. Thanks for keeping us honest, @TroyCMSSupport
@jv-agile6 as you are working on learning redirects, this may also be a good candidate to pick up. Happy to discuss if you have questions.
Following up, here. This Facility Canonical URL appears to have been removed without redirection to their Charleston VA location page and continues to be a 404 result.
Noting to self: merged yesterday, should autodeploy Monday.
The redirect has been been deployed.
Request for CSV change has been made: https://dsva.slack.com/archives/C02BTJTDFTN/p1721669125978809?thread_ts=1721421342.650609&cid=C02BTJTDFTN
This can be closed as the most recent changes to the csv have been deployed, and vha_534QA
is gone
Implementation date
When does this request need to be live: As soon as editor has confirmed KB steps -- see https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16992
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)