-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Allow adding entries to the OpenSearch keystore #76
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
base: main
Are you sure you want to change the base?
Conversation
753e529 to
c77ac69
Compare
| :description: Add entries to the OpenSearch Keystore | ||
|
|
||
| The OpenSearch keystore provides secure storage for sensitive configuration settings such as credentials and API keys. | ||
| You can populate the keystore by referencing Secrets from in your OpenSearch configuration. |
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.
| You can populate the keystore by referencing Secrets from in your OpenSearch configuration. | |
| You can populate the keystore by referencing Secrets within your OpenSearch configuration. |
| ] | ||
| .into(), | ||
| vec. |
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.
nit:
| pub keystore: Vec<OpenSearchKeystore>, | |
| /// Name of the Vector aggregator [discovery ConfigMap](DOCS_BASE_URL_PLACEHOLDER/concepts/service_discovery). | |
| pub keystore: Vec<OpenSearchKeystore>, | |
| /// Name of the Vector aggregator [discovery ConfigMap](DOCS_BASE_URL_PLACEHOLDER/concepts/service_discovery). |
| crd::{ | ||
| NodeRoles, | ||
| v1alpha1::{self}, | ||
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, |
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.
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, | |
| v1alpha1::{self}, |
| crd::{ | ||
| NodeRoles, | ||
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, | ||
| }, |
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.
| crd::{ | |
| NodeRoles, | |
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, | |
| }, | |
| crd::{NodeRoles, v1alpha1}, |
| crd::{ | ||
| NodeRoles, | ||
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, | ||
| }, |
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.
| crd::{ | |
| NodeRoles, | |
| v1alpha1::{self, OpenSearchKeystore, SecretKeyRef}, | |
| }, | |
| crd::{NodeRoles, v1alpha1}, |
| - key: s3.client.default.access_key | ||
| secretKeyRef: | ||
| name: s3-credentials | ||
| key: s3.client.default.access_key |
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.
nit: The keys in the Secret could be renamed to ACCESS_KEY and SECRET_KEY. If a test uses the same value for different fields (keystore.key and keystore.secretKeyRef.key in this case), the code could read the wrong field and the test would still be successful.
Description
Allow referencing Secret keys in the OpenSearch config to add them as entries to the OpenSearch keystore.
Part of #44.
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker