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

ability to self-manage db creds #67

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

smcavallo
Copy link

For those who deploy blackduck via helm, and maintain their helm charts and values.yaml files in source control, currently the database passwords are maintained in values.yaml.
For security best practices the postgres passwords should not be checked into source control.
This PR allows you to mark the creation of secrets as false - which will allow consumers to maintain their own <RELEASE>-blackduck-db-creds secrets using their own process and secrets management solution.
Ex.

postgres:
  createSecret: false

@skatzman-synopsys
Copy link

This is reasonable and is an improvement from a security and configuration flexibility perspective.

Internally filed HUB-32210 to backlog for prioritization.

@Chumper
Copy link

Chumper commented Oct 9, 2023

What is the priority on this? I am also looking for this. This seems like a small change, so any reason not to merge this as is?

@Chumper
Copy link

Chumper commented Oct 23, 2023

Can I assume this will not be implemented?

@m-zare
Copy link

m-zare commented Mar 4, 2024

This is a requirement for a more mature setup. Also, make the deployment possible without in-house customization as we are forced to do atm.
Can you prioritize, please?

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

Successfully merging this pull request may close these issues.

4 participants