Skip to content
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

[Workspace] Provides fundamental features from OSD core to support workspace development #5091

Closed
ruanyl opened this issue Sep 22, 2023 · 0 comments · Fixed by #5092 or #5244
Closed
Assignees
Labels

Comments

@ruanyl
Copy link
Member

ruanyl commented Sep 22, 2023

Related issues

Feature request: #1044
Future vision for Dashboards: #4298
Workspace experience & access control RFC: #4615

Description

This issue is to propose the development of fundamental features and changes in OSD core to support the development of workspace as a plugin.

Implementing the Workspace feature as a plugin is dependent on several fundamental changes to the OpenSearch-Dashboards core. These changes are necessary to ensure the seamless integration and functioning of the Workspace plugin with the existing application:

  1. Resource Association: The core should be modified to allow resources (dashboards, visualizations, etc.) to be associated with workspaces. For example, savedObjects service and savedObjectsManagement plugin should be modified to accommodate workspace features.
  2. User Interface: Fundamental changes will be required in the application's user interface to accommodate workspace-related navigation and management. Such as ChromeService module and modules under ChromeService will be modified to accommodate the workspace UI changes.
  3. Workspace State Management: Since workspace will have impact to various modules of OpenSearch-Dashboards. A core WorkspacesService module will be introduced to OpenSearch-Dashboards core to create a robust and flexible mechanism for managing and sharing workspace state across modules, ensuring a consistent behavior throughout the application.

The Goals

  1. Non-Invasiveness: We hope these changes to core are non-invasive, that means OSD should just work as it is if workspace is not enabled. The existing OSD users who don't use the Workspace feature won't experience any disruptions or performance issues due to these changes
  2. Workspace-Plugin-Agnostic: We hope these core changes are workspace-plugin-agnostic, though OSD will provide a default workspace implementation, but it can also give the community the flexibility to build customized workspace plugins.

Discussion

This proposal is open for discussion, and we welcome feedback, suggestions, and insights from the OpenSearch-Dashboards community. For core, it's crucial that the mechanisms for providing workspace experience and managing workspace state are well-defined and align with the project's goals and principles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants