-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Remove the opensearch-dashboards
module from this repo
#14500
Comments
opensearch-dashboards
module from this repoopensearch-dashboards
module from this repo
@reta Do you know the purpose of this module? A simple search for the |
I actually don't to be fair, but it says 'Plugin exposing APIs for OpenSearch Dashboards system indices' |
This might be of interest for the list of the APIs, opensearch-project/opensearch-api-specification#236. |
Please describe the end goal of this project
There is a module in core called opensearch-dashboards that appears to be unused.
This plugin is a single file and all it does is register a few RestHandlers that wrap common operations around indices. On the surface, it looks like the purpose of this plugin is to facilitate requests from OpenSearch-Dashboards to allow dashboards to write to the saved objects (.kibana or .opensearch_dashboards*) index, but its not actually used by dashboards.
When running a cluster with security, dashboards must be configured with
opensearch.username
andopensearch.password
which is used to write and read from the saved objects index or indices if using multi-tenancy. In the demo configuration, this is thekibanaserver
user which is mapped to the kibana_server role which grants it permission on those indices.This is the list of RestHandlers that it registers and it prefixes all of their existing routes with
_opensearch_dashboards/
i.e. The create index API that this plugins registers is
PUT /_opensearch_dashboards/{idx}
instead ofPUT/{idx}
Judging by the wrapper in this class it looks like the plugin is trying to provide additional protections to the saved objects indices.
If the module is unused then is there any purpose in keeping the code in core?
Supporting References
Related to work in opensearch-project/security#4439 that is analyzing system indices across all default modules and plugins
Issues
Related to opensearch-project/security#4439
Related component
Plugins
The text was updated successfully, but these errors were encountered: