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

Allow empty string for encrypted data #476

Closed
wants to merge 3 commits into from

Conversation

fallard84
Copy link
Contributor

@fallard84 fallard84 commented Mar 21, 2020

Decrypting empty string will simply return an empty string without failing. This is to support one of our use case where I have an app that I want to instantiate many times and some variant of this app don't require all secrets. Since I want to reuse the same template for the config map, I would simply put an empty string for the secrets that are not required instead of having to encrypt a dummy value for the decryptor to not fail.

Francois Allard added 3 commits March 20, 2020 19:55
Decrypting empty string will simply return an empty string without failing
@omerlh
Copy link
Contributor

omerlh commented Mar 22, 2020

Thanks for the PR! The tests are failing because we still don't have good support for PRs :( see #67). I'm fine with merging and letting the tests running on master for now.

One question I do have - how do we define a valid input. Calling a decrypt function without anything to decrypt sounds more like a bad request to me :) Maybe the fix should be in the init container? Not to send empty string at all? Unless I'm not understanding the usecase...

@shaikatz
Copy link
Contributor

Closed for being stale.

@shaikatz shaikatz closed this May 12, 2020
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.

3 participants