Add support for existing credentials

[otherguy]

Summary

It would be great if we could specify e.g. operator.existingTokenSecret and connect.existingCredentialsSecret when installing the Helm chart

Use cases

I use this with ArgoCD and don't want the credentials/token in my Git repository.

Proposed solution

Specifying the name of a Secret with the existing token should negate the need to specify token/credentials on every install.

[onedr0p]

This would be awesome, but it seems like the maintenance of this repo is lacking :/

[nklmilojevic]

Same problem with our usage at MailerLite. We imported it into Flux, but as soon as we updated the version, it broke cause it requires files each time. Please provide a mechanism for using an existing secret.

[TheOutdoorProgrammer]

I know this is old, so it may just be outdated. But I installed this no problem with a existing credentials (also using flux). If you just dont set connect.credentials or operator.token.value neither secret will be created and you can use an existing secret.

[jillianwilson]

Apologies for the slow movement on this issue, we have tracked this internally to look into adding in the future. We will update you when this has been implemented. In the meantime, is the solution that @Apollorion provided satisfactory?

[jamescallumyoung]

Any updates on this issue? I would also like to be able to provide an existing secret.

The workaround seems like a hack, and since it isn't mentioned anywhere in the docs, I'm not comfortable relying on it in production.

If the 1password team is unable to implement the feature as requested, updating the docs and committing to support this hack as an official deployment option would go a long way. (I'm happy to update the docs if this will remain a supported option.)