-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
chore(perf-issues): Add a flag and check it to allow customer to disable detectors #91734
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
chore(perf-issues): Add a flag and check it to allow customer to disable detectors #91734
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm - internal_only_settings
looks scary but is only controlling the enabled state for these detectors, once we roll this out fully I think we can clean that up
I agree about the clean up, there are a lot of magic strings around here and places you have to update when extending a detector and it's pretty easy to get wrong. |
…or-per-project-to-be-user-facing
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #91734 +/- ##
==========================================
- Coverage 87.61% 87.61% -0.01%
==========================================
Files 10335 10335
Lines 586491 586479 -12
Branches 22550 22548 -2
==========================================
- Hits 513846 513829 -17
- Misses 72199 72204 +5
Partials 446 446 |
Add tests for feature flag check implemented in #91734, forgot them there
Add tests for feature flag check implemented in #91734, forgot them there
This will be overridden by detector work later on, but expose it now so customers can understand how it might work (and disable any detectors without support tickets)