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
We plan to launch SDKs for OpenSearch and OpenSearch Dashboards, and support development of third-party extensions. Additionally, we will launch an MVP of the OpenSearch extensions Catalog in order to host extensions for users to easily find, install, and update community-developed extensions.
Building plugins is too difficult and expensive to maintain, given the key plugin challenges including version coupling, lack of out-of-box security, required restart to install, lack of dependency management and awareness, lack of inter-plugin communication, etc. Additionally, today's bundle release model creates a high barrier of entry for the community to include their plugin in the project.
Extensions solve these key disadvantages of plugins and allow us to open up and encourage feature development in the community.
Below are the major milestones leading up to launch. We will keep this issue updated with the overall progress (including dates TBD) and links to more information. Granular tracking is through the GitHub SDK Project.
Milestone 0: Extension Namespace
The purpose of this milestone is to namespace the extensions code to run separately from plugins. By the end of this milestone we can demo extensions running in the OpenSearch Dashboards UI. In the nav, we’ll see OpenSearch Extensions and a “Hello World”. When you click on Hello world it will show a page that calls an OpenSearch Dashboards API and renders text. This does not yet provide ability to call the APIs externally.
Milestone 4: Uninstalling and Dependencies (stabilization)
By the end of this milestone we can demo an extension being installed and showing no impact to stabilization of app (aka no white screen). If an extension has other extensions depending on it, we will disable the downstream extensions.
By the end of this milestone we can demo the built artifacts (tarballs) (e.g. SDK, any extension, etc). This major milestone should position the SDK for an experimental release. Our goal is to hit this milestone in June.
Milestone X: Catalog MVP
This will consist of a basic listing of extensions and other artifacts on our website. Details of this effort are still being worked on.
Milestone X: OpenSearch Dashboards - Decoupling the rigid dependency
By the end of this milestone we can demo Dashboards running with versions of OpenSearch and Plugins that are not the same version. Please review the RFC for details. We will update our milestones above as we figure out where it will land in the milestone schedule.
The text was updated successfully, but these errors were encountered:
Introduction
We plan to launch SDKs for OpenSearch and OpenSearch Dashboards, and support development of third-party extensions. Additionally, we will launch an MVP of the OpenSearch extensions Catalog in order to host extensions for users to easily find, install, and update community-developed extensions.
Building plugins is too difficult and expensive to maintain, given the key plugin challenges including version coupling, lack of out-of-box security, required restart to install, lack of dependency management and awareness, lack of inter-plugin communication, etc. Additionally, today's bundle release model creates a high barrier of entry for the community to include their plugin in the project.
Extensions solve these key disadvantages of plugins and allow us to open up and encourage feature development in the community.
Below are the major milestones leading up to launch. We will keep this issue updated with the overall progress (including dates TBD) and links to more information. Granular tracking is through the GitHub SDK Project.
Milestone 0: Extension Namespace
The purpose of this milestone is to namespace the extensions code to run separately from plugins. By the end of this milestone we can demo extensions running in the OpenSearch Dashboards UI. In the nav, we’ll see OpenSearch Extensions and a “Hello World”. When you click on Hello world it will show a page that calls an OpenSearch Dashboards API and renders text. This does not yet provide ability to call the APIs externally.
Milestone 1: Installation and Configuration
The purpose of this milestone is to demonstrate an extension being installed, configured, and running.
Milestone 2: Version Compatibility
The purpose of this milestone is to demonstrate each extension has its own version and a version compatibility matrix.
Milestone 3: Dependency Management
By the end of this milestone extensions will run without access to global_shared_deps and manages their own dependencies.
Milestone 4: Uninstalling and Dependencies (stabilization)
By the end of this milestone we can demo an extension being installed and showing no impact to stabilization of app (aka no white screen). If an extension has other extensions depending on it, we will disable the downstream extensions.
Milestone 5: OpenSearch Dashboards APIs and Lifecycle Hooks
By the end of this milestone we can demo an extension, like AD, leveraging the SDK.
Milestone 6: Experimental Release / Build Release artifacts
By the end of this milestone we can demo the built artifacts (tarballs) (e.g. SDK, any extension, etc). This major milestone should position the SDK for an experimental release. Our goal is to hit this milestone in June.
Milestone X: Catalog MVP
This will consist of a basic listing of extensions and other artifacts on our website. Details of this effort are still being worked on.
Milestone X: OpenSearch Dashboards - Decoupling the rigid dependency
By the end of this milestone we can demo Dashboards running with versions of OpenSearch and Plugins that are not the same version. Please review the RFC for details. We will update our milestones above as we figure out where it will land in the milestone schedule.
The text was updated successfully, but these errors were encountered: