Proposal: Allow custom plugin path when installing
See original GitHub issueDescribe the solution you’d like
Currently, when installing a plugin to dashboards via ./opensearch-dashboards-plugin-install file://<zip>
, the plugin folder name is automatically created using the plugin id here, which is currently required to be camel case. This will create plugin folders looking like OpenSearch-Dashboards/plugins/<camelCasePluginId>
. A camel case folder name doesn’t follow standard naming conventions within Dashboards. For example, preinstalled plugins are in snake case (see here).
I propose to either change the default created directory for installed plugins to follow the conventions of snake case, or add a field in opensearch_dashboards.json
config files for plugins to allow setting a custom plugin path.
Issue Analytics
- State:
- Created 2 years ago
- Comments:29 (29 by maintainers)
Top Results From Across the Web
Install custom plugins | Cloud Composer
To install a custom plugin into your Cloud Composer environment, copy the plugin code to the plugins folder in the Cloud Storage bucket...
Read more >Setting up custom plugin in Kubernetes environment - v2.8.x
This guide goes through steps on installing a custom plugin in Kong without using a Docker build. PermalinkPrepare a directory with plugin code....
Read more >How to Manually Install a Wordpress Plugin? - Sunny HQ
Add the plugin folder to the folder labeled wp-content/plugins folder in your WordPress directory. Go into the plugins directory to activate it.
Read more >How to Install a WordPress Plugin - Step by Step for Beginners
Extracting the plugin zip file will create a new folder with the same name. This is the folder that you need to manually...
Read more >How to Install a WordPress Plugin - Beginner's Guide
When just getting into WordPress, one of the first questions you'll ask is how to install a WordPress plugin? Today, we give you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If we can do it gradually with smaller PRs, to ensure no git history is lost as well functional tests passes on each one should be good, my only point s we can keep making progress, I remember kibana had earlier using
-
but changed to camelCase as part of new framework need to understand the reason why it is like that.Overall my point was, not to add any scope for GA, we can do it as part of 1.1 and keep making progress. Just my thoughts if we have extra bandwidth to take care we’ll take in.
@mihirsoni Don’t feel strongly about it, your call!