Description

At this moment, enabling and disabling features can be done only via the configuration options that accept a list of features. It means when a user/customer has enabled multiple preview features (or multiple disabled) and then the state needs to be changed, the user/customer needs to go over the big list and remove the feature from the list. The UX is not very good in this manner and it's also a problem in the testsuite as we need to do multiple workarounds on how to enable/disable features in these lists.

It'd be better to have a single wildcard option for these features and be possible to change the state of the feature via a single property.

We've already discussed it with @shawkins on some team meetings that would be good to have it.

Value Proposition

Improved UX, better management for the operator, and more consistent handling in the testsuite.

Goals

• provide the wildcard option
• validate these inputs
• improve the testsuite
• check how it could help in operator

Non-Goals

n/a

Discussion

No response

Notes

No response