Hide plugins from UI that don't support a satisfying end-to-end experience
I suggest adding a new boolean property to
discovery.yml that will determine whether or not the plugin is displayed in the UI by default.
If a plugin is already installed (using the CLI or the UI before this change was made), it should still be displayed so that it can be configured, but we should not suggest that the user install any plugins if we know that there's actually no way they can get to value using just the UI.
One that property exists, I think we can start by hiding:
tap-mongodb, because neither is useful without custom transforms and models which cannot be set up in the UI
All targets except for
target-postgres, because that's the only one that's fully supported by transforms and Analyze