Hi everyone,
I’m working on adding YDB as a built-in physical storage backend for Vault and would appreciate guidance from the Vault team (especially storage/core) before the PR sits too long without review.
Links
- Feature request: Add YDB as a physical storage backend · Issue #31909 · hashicorp/vault · GitHub
- Implementation PR: YDB backend by kprokopenko · Pull Request #31908 · hashicorp/vault · GitHub
- Documentation PR: Vault: Add YDB storage backend documentation by kprokopenko · Pull Request #2189 · hashicorp/web-unified-docs · GitHub
Questions
Is HashiCorp open to accepting YDB as a built-in storage backend in the core repository?
Also, is there anything we should change upfront (scope, API surface, auth methods, test approach) to make a first-pass review easier? Would splitting the PR help — e.g. core backend first, test helpers separately?
We’re happy to adjust the design or scope based on maintainer feedback. Any pointer on the preferred next step would be very helpful.
Thanks!