-
Notifications
You must be signed in to change notification settings - Fork 59
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
Better support for private keys #172
Comments
I experienced the same issue, and I have solved it with option 2 as that is already possible. This used to be in the documentation, but for some reason they removed almost all usable documentation starting in v1.7.1 and I have no idea where to find this now, but in the older docs you can see that files are supported https://github.com/1Password/onepassword-operator/tree/v1.7.0#usage |
I started to use https://external-secrets.io/ in combination with op-connect. This is much more configurable and easy to use. |
Summary
Hi, I've been really enjoying most of the UX around storing secrets in 1Password and having the connector inject them into K8. However, one area that feels like it could use some more love is the need for storing and accessing private keys. Recently, while setting up a GitHub App, I found that attempting to store the private key as a "password" field was messing up the formatting of the key, leading to an error. The only solution I have found is to store the private key as a "text" field.
It's not the end of the world, but it would be nice to either
This way, users could store their keys in a way that makes more sense than plaintext inside 1Password.
Use cases
See above
Is there a workaround to accomplish this today?
See above
The text was updated successfully, but these errors were encountered: