The InfluxDB 3 Explorer UI needs a way to indicate plugin maturity levels (beta, deprecated) to users browsing the plugin library.
Currently there's no mechanism for plugin authors to signal that a plugin is in beta or experimental status. Users have no visibility into which plugins are production-ready vs. still in development.
Requested capability: Allow plugin entries in plugin_library.json to specify a status that the UI can display as a badge.
Suggested Implementation
Add an optional status field to plugin entries:
{
"name": "Example Plugin",
"path": "influxdata/example/example.py",
"status": "beta",
...
}
Field details:
- Name:
status
- Type: string (optional)
- Values:
"beta" initially; Other values can be added later.
- Default behavior: If omitted, plugin is treated as stable/production (no badge shown)
Backward compatibility: Fully compatible - existing plugins without the field continue to work unchanged.
UI behavior: The Explorer UI will display a colored badge (e.g., orange "Beta" pill) on plugin cards for plugins with a status set.
The InfluxDB 3 Explorer UI needs a way to indicate plugin maturity levels (beta, deprecated) to users browsing the plugin library.
Currently there's no mechanism for plugin authors to signal that a plugin is in beta or experimental status. Users have no visibility into which plugins are production-ready vs. still in development.
Requested capability: Allow plugin entries in
plugin_library.jsonto specify a status that the UI can display as a badge.Suggested Implementation
Add an optional
statusfield to plugin entries:{ "name": "Example Plugin", "path": "influxdata/example/example.py", "status": "beta", ... }Field details:
status"beta"initially; Other values can be added later.Backward compatibility: Fully compatible - existing plugins without the field continue to work unchanged.
UI behavior: The Explorer UI will display a colored badge (e.g., orange "Beta" pill) on plugin cards for plugins with a status set.