fix: report correct state of feature flags on TUI

[ossdhaval]

On a fresh install of Janssen Server(build: 1.0.21-nightly), feature flags are shown as below in TUI.

All checkboxes are unchecked. Giving an impression that all flags are disabled. At the same time, on AS all the flags are enabled by default.

We need to fix this inconsistency. TUI should always show which flags are enabled/disabled on AS. There has to be a way of TUI to know which all flags are available on AS and out of those, which ones are enabled at that point in time.

Context: discussion here

[ossdhaval]

Tagging relevant members for discussion: @pujavs @yuriyz @devrimyatar @nynymike

[yuriyz]

If "featureFlags" configuration is absent or if it has no values then AS consider it as everything is enabled. To keep it clear to end user I guess we can do following:

• All features enabled [x]
• Enable only particular AS features:
  • End Session [ ]
  • other flags below....

What do you guys think ?

[devrimyatar]

I think we are trying to determine which flags should be enabled when jans installed.

[yuriyz]

By default we don't specify any specific flag, Means no values for "featureFlags" which for AS means everything is enabled.
So default behavior is everything is enabled. It's under admin responsibility to start swithing on/off features if needed.

We can start maintaining that list and simply put all values there but then each time new feature flags is added we will need to remember to update it. Current approach is better because we don't need to maintain it. However I agree with Dhaval that we can't simply show everything unchecked while in fact everything is enabled. That's why I'm proposing solution described above with "All features enabled [x]" which should solve end-user confusion.

[yurem]

I agree with @yuriyz It's better to enable all by default and disable only specified. This will work fork new components as well

[devrimyatar]

Okay, I am going to check all flags if config-api does not return property featureFlags