[BUG] Names don't adhere to plugin naming convention

[dblock]

What is the bug?

We have published a plugins naming convention to https://github.com/opensearch-project/opensearch-plugins/blob/main/CONVENTIONS.md#plugin-naming-conventions in #56, but are failing to adhere to these consistently

• index-management-dashboards-plugin
• observability
• security-analytics-dashboards-plugin
• security-dashboards-plugin
• dashboards-maps
• dashboards-visualizations
  ...

What is the expected behavior?

Plugins follow the convention.

1. Evaluate and publish the delta.
2. Update contentions if needed.
3. Align all names to the convention.

• [BUG] Repo name doesn't adhere to plugins naming convention index-management-dashboards-plugin#415
• [BUG] Repo name doesn't adhere to plugins naming convention alerting-dashboards-plugin#372
• [BUG] Repo name doesn't adhere to plugins naming convention security-analytics-dashboards-plugin#187
• [BUG] Repo name doesn't adhere to plugins naming convention security-dashboards-plugin#1232
• [Decide] how do we name , organize and build visualization plugin/ widgets dashboards-visualizations#130 (comment)
• [BUG] Names don't adhere to plugin naming convention alerting#687
• [BUG]Names don't adhere to plugin naming convention ml-commons#847
• [BUG]Names don't adhere to plugin naming convention geospatial#252
• Rename and add a script to update version to match OpenSearch Dashboards dashboards-i18n#22
• [BUG] Names don't adhere to plugin naming convention asynchronous-search#209

[elfisher]

@mnkugler could you help pick this one up?

[mnkugler]

@elfisher sure!

[elfisher]

@elfisher sure!

Thanks!

[mnkugler]

Can anyone comment on the implications of renaming a plugin? For example, how do we handle existing dependencies? With an alias?

[davidlago]

May the first brave team renaming their plugin serve as a tracer bullet for this 🎖️

If this ends up being bigger than a breadbox, we should have the discussion around whether the juice is worth the squeeze especially for plugin repos given that we are thinking of what the next iteration of plugins would be and they might be on a (albeit long) deprecation path. 🤔

[macohen]

Oh man. Renaming plugins sounds like a painful process. But, can we ensure that naming is consistent moving forward? In what cases from the CONVENTIONS.md doc does "These are recommended plugin naming conventions. YMMV." really apply if we do want consistency?

[dblock]

+1 on getting rid of YMMV

[mnkugler]

Here's a summary of the most noticeable deviations from the conventions.

Plugin	Issue (links to the rule in CONVENTIONS.md)
Index Management Dashboard	Remove plugin from the repo name
Alerting Dashboard	Remove plugin from the repo name
Security Analytics Dashboard Plugins	Remove plugin from the repo name
Security Dashboard Plugin	Remove plugin from the repo name
Dashboard Maps	Folder needs to be fixed
Dashboard Maps	Plugin ID needs to be lowercase camelcase
Dashboard Maps	Meta needs to be updated to match the plugin name
Dashboard Visualization	Folder needs to be fixed
Alerting	Folder needs to be fixed
SQL	Folder needs to be fixed
Common Utils	opensearchplugin metadata is missing from build.gradle
Performance Analyzer RCA	opensearchplugin metadata is missing from build.gradle
ML Commons	opensearchplugin metadata is missing from build.gradle
Geospatial	opensearchplugin metadata is missing from build.gradle
i18n	Remove plugin from the repo name
i18n	Plugin ID needs to align with convention with camel case, e.g., i18nDashboards