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: San Antonio-Southwest Military VA Clinic #16504

Closed
9 of 11 tasks
stefaniefgray opened this issue Dec 19, 2023 · 4 comments
Closed
9 of 11 tasks

URL Change for: San Antonio-Southwest Military VA Clinic #16504

stefaniefgray opened this issue Dec 19, 2023 · 4 comments
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.

Comments

@stefaniefgray
Copy link
Contributor

stefaniefgray commented Dec 19, 2023

Implementation date

When does this request need to be live:
Once main ticket is ready to go (waiting for VAST): #16502

  • 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 weekly on Wed. 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.

Implementation date

When does this request need to be live: Whenever possible

Redirects

Current URL Redirect Destination or New URL
https://www.va.gov/south-texas-health-care/locations/san-antonio-southwest-military-va-clinic https://www.va.gov/south-texas-health-care/locations/

Use one of the following:

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

URL removal example (update with actual ID and URL to remove)

Facility API ID Full VA.gov URL
vha_671GK02 https://www.va.gov/south-texas-health-care/locations/san-antonio-southwest-military-va-clinic

Team

Please check the team(s) that will do this work.

  • CMS Team
  • Public Websites
  • Facilities
  • User support
@github-actions github-actions bot added Facilities Facilities products (VAMC, Vet Center, etc) User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. labels Dec 19, 2023
@stefaniefgray
Copy link
Contributor Author

See main ticket: #16502

@omahane
Copy link
Contributor

omahane commented Dec 28, 2023

Redirect request made. Node has "Awaiting redirect flag"

@stefaniefgray stefaniefgray changed the title URL Change for: San Antonio-Southwest Military VA Clinic [Waiting for VAST] URL Change for: San Antonio-Southwest Military VA Clinic Dec 28, 2023
@jilladams
Copy link
Contributor

Redirect merged, but missed weekly deploy. I may be requesting OOB on behalf of Public Websites stuff, and if so, I'll update this ticket. If not, this'll go next week.

@jilladams
Copy link
Contributor

Redirect deployed this week, flag removed in CMS. CLosing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc.
Projects
None yet
Development

No branches or pull requests

3 participants