-
Notifications
You must be signed in to change notification settings - Fork 10
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
[PROPOSAL] Granular details about the released clients #50
Comments
prudhvigodithi
changed the title
[PROPOSAL] Granular details about the clients released
[PROPOSAL] Granular details about the released clients
Feb 9, 2023
Releases for it are not yet automated, but there's also the Rust client published to crates.io: https://crates.io/crates/opensearch |
I would welcome a PR into the README of this repo. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you proposing?
We release several clients today that solves multiple problems, but we dont have detailed information and granular level details about the clients we release, what format we release and their location to download.
What users have asked for this feature?
In general this would be a one stop shop to look for and download the clients that gets released.
What problems are you trying to solve?
What is the user experience going to be?
This idea of having all clients at one place would directly help users identify the right tool/client for a purpose and directly route them to the download location.
What will it take to execute?
A document in
main
branch of this repo detailing about the different clients we release today.Captured Granular details of existing released clients (might be more if I missed).
Docker: (Not directly a client, but a format of the product we release today, open to exclude this from the list)
Ruby: https://rubygems.org/profiles/opensearchproject
Python: https://pypi.org/user/OpenSearch/
NPM:
GO:
Nuget:
Maven:
PHP:
Rust:
Terraform provider
The text was updated successfully, but these errors were encountered: