-
Notifications
You must be signed in to change notification settings - Fork 520
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
Add LTR into available plugins documentation #9298
Add LTR into available plugins documentation #9298
Conversation
Remove the custom installation step in LTR since it is avialble out of the box Signed-off-by: rithin-pullela-aws <rithinp@amazon.com>
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Signed-off-by: rithin-pullela-aws <rithinp@amazon.com>
Need to backport to 2.19 as well. Thank you! |
Change the version part in description ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay!
@JohannesDaniel would merging this change any other docs in the LTR plugin? Now that it ships with OpenSearch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @rithin-pullela-aws! Just one suggestion.
Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Rithin Pullela <rithinp@amazon.com>
@epugh @JohannesDaniel In the documentation, we are shifting to describe features rather than plugins. Of course, there are places that you need to mention that this feature resides in a plugin: for example, in installation instructions. But overall, if the plugin ships with OpenSearch, we don't need to mention it as a plugin. |
* Add LTR into available plugins documentation Remove the custom installation step in LTR since it is avialble out of the box Signed-off-by: rithin-pullela-aws <rithinp@amazon.com> * Remove copy bar at the bottom Signed-off-by: rithin-pullela-aws <rithinp@amazon.com> * Update _install-and-configure/plugins.md Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Signed-off-by: Rithin Pullela <rithinp@amazon.com> --------- Signed-off-by: rithin-pullela-aws <rithinp@amazon.com> Signed-off-by: Rithin Pullela <rithinp@amazon.com> Co-authored-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> (cherry picked from commit 9a74784) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Remove the custom installation step in LTR since it is available out of the box.
Issues Resolved
Closes #[delete this text, including the brackets, and replace with the issue number]
Version
2.19 and further.
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.