Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL Change for: Tulare VA Clinic to Visalia VA Clinic #18141

Open
16 tasks
omahane opened this issue May 16, 2024 · 0 comments
Open
16 tasks

URL Change for: Tulare VA Clinic to Visalia VA Clinic #18141

omahane opened this issue May 16, 2024 · 0 comments
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Redirect request User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. VA.gov frontend CMS team practice area

Comments

@omahane
Copy link
Contributor

omahane commented May 16, 2024

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.)

  • Notify VA stakeholders as appropriate.
  • Link the related facility closure / rename issue.
  • Create a URL redirect in the devops repo in ansible/deployment/config/revproxy-vagov/vars/redirects.yml
  • 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.
  • 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.)
  • Update this ticket with a comment that the redirect has been deployed.
  • 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.
  • 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

  • Verify that the new URL for the facility is published and accessible on VA.gov.
  • Update the CSV in Lighthouse with the changed URL, maintaining the sorted order of the Facility API IDs.
  • Create a PR in the lighthouse-facilities repo, tagging the Lighthouse team.
  • Post a message in the #cms-lighthouse channel in Slack, with an @mention to a Lighthouse team member.
  • Add the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
  • Validate that the change has deployed by checking that the Facility Locator has been updated with the new url.
  • Update this ticket with a comment that the CSV change has been deployed.
  • 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
@omahane omahane added VA.gov frontend CMS team practice area Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. Redirect request labels May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Redirect request User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

1 participant