-
Notifications
You must be signed in to change notification settings - Fork 71
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
[GitHub Request]Creation of new opensearch-storage-encryption
plugin repo
#286
Comments
Pending discussion on the naming with requester. Thanks. |
Gulshan – https://github.com/kumargu Will send invite for shubhmkr-amazon and asonje later. |
LF ticket on creating the repo first: |
LF ticket invites: |
Hi @shubhmkr-amazon and @asonje please accept your invites. Thanks. |
Hi @peterzhuamazon , |
Thanks @shubhmkr-amazon , pending @asonje confirmation before moving to next step. |
Confirmed @asonje already accept the invitation now. Repo is public: https://github.com/opensearch-project/opensearch-storage-encryption Please see the email exchange for next steps. Thanks! |
What is the type of request?
Repository Management
Details of the request
Hi,
We are working on index-level encryption support. Currently, the changes are implemented in the OpenSearch repository itself. We want to decouple this plugin from OpenSearch and create a stand-alone plugin under the OpenSearch project. Can you please help and create a repository for the same.
Repo Name: opensearch-storage-encryption
The changes are currently present and have been worked on in
PR: opensearch-project/OpenSearch#12902
Proposal: opensearch-project/OpenSearch#3469
Additional information to support your request
Decouple plugin development and maintenance from OpenSearch repo.
When does this request need to be completed?
Timely, but not urgent. Within a week is fine.
Notes
Track the progress of your request here: https://github.com/orgs/opensearch-project/projects/208/views/33.
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!
The text was updated successfully, but these errors were encountered: