-
Notifications
You must be signed in to change notification settings - Fork 70
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
Audit feature toggles for opportunities to retire #10350
Comments
This should be done on a joint call with PWS, Facilites and Dave Conlon as well as a CMS engineer and a FE engineer from both teams. On the call, engineers will need to search all three code bases for each flag to determine if they are used anywhere and can be removed.| Include audit of CMS internal toggles with this same team |
Meeting held today 08/30. @swirtSJW @jilladams who is doing the summarizing task steps and taking stab at effort? |
@dsinla a Facilities front-end engineer will need to look through the list of Flippers owned by Facilities team, most likely. |
Closing - audit completed. Executing will be done next sprint #10656 |
Description
Request from @RachalCassity:
Console Services Team is evaluating site performance, and identified feature toggles in vets-api and vets-website repos.
Feature toggles endpoint is called multiple times per page, and causes Sentry errors / site latency.
8 of the 12 feature toggles on this list explicitly identify facility_locator:
Link to Slack convo
Related PW ticket
Acceptance Criteria
CMS Team
Please check the team(s) that will do this work.
Program
Platform CMS Team
Sitewide Crew
⭐️ Sitewide CMS
⭐️ Public Websites
⭐️ Facilities
⭐️ User support
The text was updated successfully, but these errors were encountered: