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 support for optional secrets using flag optional-secrets #160

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

manherna
Copy link
Contributor

Add support for optional secrets which are not required by default.

related to #152

@manherna
Copy link
Contributor Author

Hi @arttor! It took me a while, but I found time to push this PR. What do you think? Does it suit the project scope? Does it lack anything?

Copy link
Owner

@arttor arttor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi, thank you for this proposal.
Can you please explain how optional secrets will be used?

I am asking only because i had different understanig based on our disucssion in #152.
My understanding was that:

  1. User provides list of secret names as flag. These secrets should be created externally and not be a part of Helm chart.
  2. Helmify will ignore listed secrets entirely and will not create any templates for these secrets
  3. Helmify will find secret usages in other resoruces like Pod and replace it with a name of external secret, which will be stored in values.yaml as
    externalSecrets:
        <secret_name>: "<secret_name>"

examples/app/templates/my-secret-ca.yaml Outdated Show resolved Hide resolved
@manherna
Copy link
Contributor Author

manherna commented Jan 9, 2025

Hi @arttor what do you think? Can this be merged?

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.

2 participants