Skip to content
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 an option to use preexisting secrets for connection parameters #556

Open
t0ffel opened this issue Feb 18, 2025 · 0 comments
Open

Add an option to use preexisting secrets for connection parameters #556

t0ffel opened this issue Feb 18, 2025 · 0 comments

Comments

@t0ffel
Copy link

t0ffel commented Feb 18, 2025

Is your feature request related to a problem? Please describe.
I'm deploying datahub via argocd and I'm using external cloud services for elasticsearch/mysql/kafka.
Right now I need to pass the connection strings for all the services via helm values.
It would be much easier for me to specify pre-created secrets which would contain all the connection info, rather than specify via values. (It would be easier because the secrets would be autopopulated from cloud secrets with external-secrets operator)

Describe the solution you'd like
Instead of specifying

global:
  elasticsearch:
    host: ...
    port: ...
    useSSL: ..
    auth: ...

I want to specify something like:

global:
  elasticsearch:
    externalSecret: <secret_name>

where the secret contains:

host: ..
port: ...
useSSL: ..
auth: ...

Describe alternatives you've considered
n/a

Additional context
n/a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant