Description
Can we use the :default_plugin: setting to accurately distinguish between elastic-supported and community-supported plugins.?
- Are all plugins that are installed by default elastic-supported plugins?
- Are there any elastic-supported plugins that are not installed by default?
We can most likely implement this initiative by updating plugin headers to show different text based on the :default_plugin: value.
Update: This approach won't work because there's not a 1:1 relationship between default plugins and level of support. I'm trying something different as noted in comments.
Proposal: Phased rollout
Follows the Logstash Plugins support matrix. If we use this approach, let's consider a phased rollout:
- Tier 1 plugins (72 total)
- Tier 2 plugins (17 total)
- Community
Possible next steps
We could consider adding the configuration to [plugins-metadata.json](https://github.com/elastic/logstash/blob/main/rakelib/plugins-metadata.json), but we'd still need to clear the setting in each doc source file. So there's probably no value in that approach.