Skip to content

Add built-in support for HashiCorp Vault in Aspire CommunityToolkit #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
max2020204 opened this issue May 26, 2025 · 0 comments
Open

Comments

@max2020204
Copy link

Related to an existing integration?

Yes

Existing integration

ParameterResource / Environment configuration

Overview

HashiCorp Vault is a widely-used tool for managing secrets, access tokens, encryption keys, and dynamic credentials.

Currently, Aspire supports environment-bound parameters (AddParameter(...)) and secrets via user-defined env vars, but lacks native support for a centralized secret store.

Adding a Vault integration would enable secure and flexible secret management for distributed apps using Aspire, supporting development and production parity.

Usage example

builder.AddVault("vault")
.WithToken("s.vault-token") // or link to secret parameter
.WithSecret("database-password", out var dbPassword);

builder.AddPostgres("db")
.WithPassword(dbPassword);

Breaking change?

No

Alternatives

Currently, developers have to run Vault externally and manually inject secrets as environment variables into Aspire projects. This results in duplication, potential leaks, and lack of shared secret orchestration within the Aspire application model.

Additional context

Vault supports secret engines like KV, dynamic DB credentials, PKI, and more. It would be a powerful addition to Aspire's growing ecosystem of observability and configuration tools.

Docker image: hashicorp/vault:1.15
Website: https://www.vaultproject.io/

Help us help you

Yes, but only if others can assist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant