Ask HN: Who is using 1Password for secret management?
4 comments
We use both the 1Password CLI and 1Password Connect.
The CLI tool is handy for retrieving secrets from your vaults in the CLI, handy for one-off uses like scripts etc.
The Connect server is more suited for infrastructure secrets and allows you to whitelist which vaults are available through it. You can then use secrets exposed from Connect as part of your Docker image build process on CI, for example.
The CLI tool is handy for retrieving secrets from your vaults in the CLI, handy for one-off uses like scripts etc.
The Connect server is more suited for infrastructure secrets and allows you to whitelist which vaults are available through it. You can then use secrets exposed from Connect as part of your Docker image build process on CI, for example.
I was thinking about doing this, not sure of the pros/cons. Eg moving all the secrets to 1Password, and having a simple internal cli tool for my team to push them to Github Secrets and/or just access them from 1Password in Github workflows
Interested if others have feedback
Interested if others have feedback
We are looking at the same thing. It seems like a great solution but this is new territory for me and my team.
There are a few resources there, so I guess it's supported: https://developer.1password.com/docs/cli/secrets-config-file...
https://developer.1password.com/docs/cli/secrets-scripts/
https://developer.1password.com/docs/cli/secrets-scripts/
Is anyone using it? Are there any caveats? Service account or proxy setup? Which is best?