HashiCorp Vault integration: under consideration
We’re considering a HashiCorp Vault source integration, initially focused on explicitly selected static secrets. This connector is not available today. Vault already supports workload authentication, policies and secret-access auditing; the proposed benefit is a consistent agent-facing retrieval workflow, not a replacement for those controls. No support for dynamic credentials, lease renewal or all Vault secret engines is promised.
When might a Vault retrieval layer be useful?
Established platform teams may already have suitable workload identities, policies and deployment tooling. For them, adding a hosted reader could create more work than it removes. A developer connecting agents across clients might still benefit from a common interface, provided the client accepts the access model and network path. Any pilot would need to demonstrate that benefit against direct Vault integration, including operational ownership when a token expires or the source is unavailable.
Integration considerations
- 1
Vault supports policy-bound machine authentication, including AppRole. A potential integration would need a dedicated identity and only the read capabilities required for explicitly selected static-secret paths.
- 2
KV version, mount path, field references and any namespace would need explicit handling. A proposed initial static KV adapter would not imply compatibility with every Vault engine or managed product.
- 3
Private-network reachability and TLS trust would need a client-approved design. There is no current Gazebo tunnel or customer-operated Vault connector to configure.
- 4
Authentication-token expiry, sealed or unavailable Vault and denied paths require safe failure behaviour. Dynamic credentials add a separate lease and renewal lifecycle that is outside the proposed initial scope.
- 5
Vault audit records can describe source access; provider records are needed for subsequent use. Removing a reader or agent grant would not retract a static secret already delivered to a process.
Workflows we’re evaluating
Selected static-secret retrieval
A potential connector could expose approved static-secret references through the same agent-facing contract used for other sources. The client would still control Vault policy and source-reader access, and the agent runtime would still receive the actual provider credential.
Consistent client integration
For an agency supporting different client infrastructures, a common retrieval contract might reduce repeated adapter work. Before building, we would need to establish whether the client permits the trust relationship and whether native Vault tools already solve the workflow with less complexity.
Discuss your HashiCorp Vault workflow
Tell us about your vault, agent runtime and integration needs. Please don’t send credentials or sensitive client information. No connector or launch date is promised.
Discuss your HashiCorp Vault workflow