For servers tools, maybe people wrote cool stuff at work but they are not published.
For servers tools, maybe people wrote cool stuff at work but they are not published.
IIRC HashiCorp was not interested in supporting these kinds of tools because they were in direct competition with the Vault enterprise offering.
The biggest missing piece back then was lack of a search feature and the maintainers were not interested in implementing it.
In all seriousness, you may want to open an issue <https://github.com/openbao/openbao/issues> as they have weighed in on a few threads here saying they're open to suggestions
Having implemented a reader for 1Password's "old" opvault format, I would imagine the threat model is not just searching, so it may be a heavy lift to coerce ~~Vault~~ OpenBao's mental model over into one that can be used as a consumer a password manager but I'll admit that would be pretty cool to unify vaultwarden and OpenBao into one stop shopping for all one's cryptographic needs
It also inspires confidence for new adopters. I was often wondering with vault "why are there so few 3rd party tools? Is almost nobody using vault or people just use their own private tools". I was afraid to "invest" by using a tool that I perceived as not being popular enough and maybe have a limited future (maybe just in the 3rd party tools area)
Feel free to ignore the Nix stuff, but I’ve outlined how I create entries with the 1Password CLI: https://github.com/heywoodlh/flakes/tree/main/kube#1password...
After a OnePasswordItem is created, a secret containing your fields and their values appears. It’s marvelous!
(Integrations like this are why I switched away from Bitwarden to 1Password)