elastic
[Fleet] Hide deprecated features for integrations at fresh installs
Sometimes we can't delete a deprecated data stream or input because a breaking change like that would impact the user experience that is currently using that deprecated feature.
For these cases, we would like to be able to hide that deprecated feature for new installations.
For instance, in the case above, we are not able to hide the deprecated option for the O365 integration.
This would require changes at Kibana and spec levels.
Can we also have a better way to distinguish between deprecated and recommended data streams?
If you check the image above the only distinction is the Deprecated. word in data stream description, this is not enough to deter users from using it. Can the full description text be greyed out or in an orange color to signal the state of the data stream better?
Can the existing users see a warning message in the Installed Integrations list that the data stream they are running is deprecated etc.
Users not migrating away from deprecated features makes it impossible for us to remove them and focus on new functionality.
Also a Deprecated category in the integration list, to hide all deprecated integrations by default or filter by.
FYI @criamico I moved this to a child item of https://github.com/elastic/package-spec/issues/227 as it seems more related to that set of work. We'll be able to support this filtering once the deprecated flag is wired up as part of that effort.
