search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
98 stars 68 forks source link

Enable non-code updates to Veteran Crisis Line phone number #11783

Open wesrowe opened 1 year ago

wesrowe commented 1 year ago

Description

On 12/1 the national mental health line 988 went down, forcing VA to do an emergency code change to change the number. The overhead was really high – it took 2 hrs to get code merged and then rounding up approvals for an OOB deployment around 8pm ET. There was a realistic risk that it might have been even further delayed. This affects one of the VA's highest priorities: making sure Veterans in crisis can get support.

Could Drupalize. (Could also put backup number behind a flipper?) It would enable updates with minimal people involved and just a content build to publish.

Note: there are possibly several ways to solve this. The Dev who pick this up will investigate.

Acceptance Criteria

CMS Team

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

swirtSJW commented 1 year ago

Good candidate for the us of Centralized Content type.

jilladams commented 10 months ago

@FranECross this ticket assumes some pre-work in Drupal that isn't indicated here as a blocker. We may need to find / link or create that ticket if it doesn't exist.

jilladams commented 10 months ago

Blocked on Drupal.

FranECross commented 10 months ago

@jilladams Question about the drupal ticket needed per comment above 😁, would the ticket description just be something like "Drupal work in support of enabling non-code updates to the Veteran Crisis Line phone number"? Thanks in advance!

jilladams commented 10 months ago

It's a good question - I think we need to get engineering help to understand what the options/ ideal workflow might be here, in order to know. Right now, if the VCL needs changes, we have to update code. In order to make it possible to update that content without having to deploy code changes, we need to figure out the alternatives and the effort required for them. We could put it in Drupal -- there's not a totally obvious right place / way to manage that info in Drupal. Wes also mentioned a FE option in the ticket body here using flipper, and I'm not totally sure I understand how that might work.