-
Notifications
You must be signed in to change notification settings - Fork 503
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 documentation for Crypto plugin #4389
Conversation
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
A first draft has been sent for tech review. But this includes some last questions, which will probably require changes. |
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
Signed-off-by: cwillum <[email protected]>
@vikasvb90 Could have a look at this for technical accuracy. Also, there's one outstanding question about the Cypto plugin repo. Do you have a link to this yet? Thanks. |
Crypto plugin has been pushed to 2.10. |
Development team is currently refining the plugin for OpenSearch applications. No documentation needed for 2.10. |
I'm assuming that we should not include this in the release notes? I removed the flag. |
The issue was closed, so closing this PR. |
Description
A new Crypto plugin for client side encryption and decryption of data for remote transfer / remote store.
Issues Resolved
Fixes #2995
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.