Add config to disable the Fully Enable button

[elShiaLabeouf]

Hi!

I'm proposing to add two new configuration options for Flipper::UI to allow disabling the Fully Enable button.

Use case

When rolling out features gradually (i.e. test group first, then wider), there are cases where fully enabling for everyone isn't appropriate - for example, when certain users have opted out of receiving new features. This configuration prevents accidental full rollouts.

Demo

Default behavior (config.fully_enable_disabled is false by default):

Disabled button & default tooltip:

Flipper::UI.configure do |config|
  config.fully_enable_disabled = true
end

Disabled button & custom tooltip:

Flipper::UI.configure do |config|
  config.fully_enable_disabled = true
  config.fully_enable_disabled_with = '<Custom disabled message>.'
end

[jnunemaker]

I'm not sure I understand why. Why would you not eventually fully enable a feature?

[elShiaLabeouf]

Hey @jnunemaker, thanks for the quick response! :)

Our project is actively developing, the feature set is expanding, the design is changing; and while most of the users are happy with such active support, a small percentage of them would prefer to keep the product minimalistic. I would very much like to fulfill their wishes since it's easy - we'll just leverage a Flipper group "everyone except these guys". At the same time, I want to minimize the chance of someone accidentally fully enabling a FF for everyone - that's where disabling the button would come in handy.

Please share your thoughts on the proposal! Maybe there's a better way to achieve this goal?