-
Notifications
You must be signed in to change notification settings - Fork 683
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
Unseal templates even when encryptedData is empty #653
Unseal templates even when encryptedData is empty #653
Conversation
@twz123 nice pr but looks like no one from bitnami will review |
hi @twz123 Let me investigate a little bit to understand the change in the code and I will review it. I am going to be one of the maintainer in charge of the review. Sorry for the delay Thanks a lot Álvaro |
hi @twz123 Could you do a rebase, please? The PR was created before to fix the pipeline and the checks jobs are blocked. Just to verify that we are not breaking anything. Thanks Álvaro |
Introduce some utility functions to make tests more concise.
Previouly, SealedSecrets with empty encryptedData fields but with non-empty template.data fields were unsealed into empty Secrets. Change this by removing the check for non-empty encryptedData fields.
62d2fa1
to
89dbfc8
Compare
@alvneiayu rebased as requested |
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.
LGTM, do you have any concern about this @mkmik @juan131 @agarcia-oss?
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.
LGTM! Awesome, thanks so much for this great PR
Previously, SealedSecrets with empty encryptedData fields but with non-empty template.data fields were unsealed into empty Secrets. Change this by removing the check for non-empty encryptedData fields.