Having secrets in bitwarden is good and all, but currently there’s a lack of places the secrets can actually be used. Github Actions is a good first one, however there are more integrations required to make this useful to us.
This was a core consideration in why my organization selected 1Password over Bitwarden.
The capabilities of the 1Password Operator and Secrets Injector are very mature and are allowing my team to commit secrets configuration to source control without risk of secrets. Below is an example manifest.
Thanks, @estenrye. We appreciate the feedback and the sample manifest. Expanding integrations support is a continued product focus for Bitwarden Secrets Manager, with the Kubernetes operator being the top priority - you can expect the release in the coming months. I will update this thread as we get closer to launch.
It would be great to have a list of pending integrations on your help section (https://bitwarden.com/help/github-actions-integration/), along with approximate timelines. We’re very interested in the kubernetes integrations.