You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
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
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
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.
The text was updated successfully, but these errors were encountered:
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:
savedObjects
service andsavedObjectsManagement
plugin should be modified to accommodate workspace features.ChromeService
module and modules underChromeService
will be modified to accommodate the workspace UI changes.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
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.
The text was updated successfully, but these errors were encountered: