-
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
Evaluate flipper facilities_ppms_suppress_all for removal #11589
Comments
This flipper exists so that if there are problems with the Provider Profile Management System (PPMS) we have the ability to disable all the front-end search interfaces that rely (either fully or partially) on data from PPMS.
|
@jilladams @FranECross @mmiddaugh This flipper audit was done in late 2022. Would it even still be accurate? Are we realistically going to chase this work at any point? |
I don't know how to answer. Does the Platform definitely want us to be removing unused Flippers due to performance overhead on the VA.gov site? Yep. Will we ever choose to prioritize this work? ...I'm not sure. Can we walk away from the tech debt just because we don't intend to prioritize it? ...dunno. If the Platform ever got worked up about Flipper performance again, and put pressure on teams to remove their old flippers: we would definitely have to prioritize this work and the other tickets like it. 🤷♀️ |
Makes sense. Backlog seems like a good place for it for now. |
Will not remove. Will keep for long-term use. Closing as no op and #11591 will track updates on the flipper to document that in the flipper ui. |
Description
Investigate facilities_ppms_suppress_all flipper for current use and eligibility for removal.
Refer to #10656
Tasks
The text was updated successfully, but these errors were encountered: