-
Notifications
You must be signed in to change notification settings - Fork 59
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
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin #2311
Comments
Decision MadeWe aren't removing 1) Log Explorer, 2) Observability Dashboards, and 3) App Analytics in the 3.0 release. The main reason being Discover 2.0 doesn't support the creation of PPL visualizations. While this feature gap is being worked on, we plan a phase-wise deprecation starting with the Observability backend plugin and later extending to each of these plugin sub-components. We plan to remove the above-mentioned plugin components in OpenSearch Dashboards version 4.0, where we expect to have 1:1 feature parity with the alternatives we expect users to use. Meanwhile we still are planning to remove the legacy notebooks support for 3.0 version as outlined below. Also, Legacy client deprecation from core is moved out of 3.0 plan. So no changes required here for now. Features to be removed in 3.0
These are proposed changes based on discussion with @mengweieric @joshuali925 @vamsimanohar |
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.
Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.
If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.
Overall, this would help us deliver a smooth and seamless upgrade experience.
Thanks.
The text was updated successfully, but these errors were encountered: