fix: credential secret does not works if set from values

[grhawk]

Same as #113 with verified commit.

[jillianwilson]

Hey @grhawk ! Thanks for creating the new PR! Looks like there are some merge conflicts here. Do you mind taking a look at those?

[grhawk]

@jillianwilson sorry, I don't remember out of my head what I did there since it is about 2y old and I don't have much time to re-look into it from scratch :)

[stewartmalik]

I'm actually not sure that this one is required, 1Password/connect#62 seems to suggest that connect requires the value to be doubly base64 encoded.

I have run the chart test suite successfully without these changes and everything worked as expected, I was able to retrieve my secret value.

[grhawk]

I think a doubly encoded secret looks more like a workaround than a solution and generates annoying effects. For example, all tools that allow to see secrets will not work properly since they expect the secret to be encoded only once.

[grhawk]

@jillianwilson I think you already fixed the conflicts in the previous MR. See adcbeff

[smauermann]

Bump, I would love for this to be merged. Without a fix to the double base64 encoding situation it is really hard bootstrapping onepassword connect in a GitOps environment. 🙏

[Piwero]

any uptdate on this PR? many people waiting for this @jillianwilson