You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Name and Version
bitnami/harbor 24.0.2
What architecture are you using?
amd64
What steps will reproduce the bug?
helm template --set registry.secret=0123456789abcdef harbor-24.0.2.tgz | grep REGISTRY_HTTP_SECRET
PG5pbD4=
, when decoded equals<nil>
Are you using any custom parameters or values?
Yes, I'm overriding the
registry.secret
value (but I'm not assigning theregistry.existingSecret
value)See "steps to reproduce" above.
What is the expected behavior?
The
Secret
created should include a keyREGISTRY_HTTP_SECRET
with the value provided in the overrideWhat do you see instead?
PG5pbD4=
, when decoded equals<nil>
Additional information
It looks like this bug was introduced by the fix for #29372, where the following lines cause the current problem:
If there is no existing secret, then
$registryHttpSecret
will be null, but theif
statement checks for the empty string, which is not the same thing.The text was updated successfully, but these errors were encountered: