-
Notifications
You must be signed in to change notification settings - Fork 167
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
[Feature Request]: Rework Feature Flags #1108
Comments
Feature flags for Bias and Performance have been handled as part of their respective Trackers see: EDIT: I think I missed the point of this ticket in my initial reading, this is about improving how flags are implemented not merely implementing them for given features. |
@alexcreasy Yeah, we want to rework this |
@andrewballantyne yeah, they're just the usual: |
Migrated to: https://issues.redhat.com/browse/RHOAIENG-2457 |
Feature description
Our DashboardConfig is v1alpha1. I recommend we change that to v1alpha2 and rework the way our feature flags are stored.
We want to go to a highly customized structure of feature flags so things can be picked and chosen to be turned on / off.
I recommend something like:
(see #1109 for more on metric namespace)
There are features that are built on others -- and I think we need to look at tying them together. True here and False there, that could mean they are both False because features are dependant on each other.
We also need to talk about how features are just not going to work without other unrelated but tied in features. Projects are a huge basis of what we are doing going forward. If projects are disabled -- what then?
Describe alternatives you've considered
We keep what we have and it grows out of control slowly as we add more features related to each other.
Anything else?
No response
The text was updated successfully, but these errors were encountered: