Skip to content

feat: HashiCorp Vault settings - #154

Open
larrywax wants to merge 1 commit into
pgdogdev:mainfrom
larrywax:vault-support
Open

larrywax wants to merge 1 commit into
pgdogdev:mainfrom
larrywax:vault-support

Conversation

@larrywax

@larrywax larrywax commented Oct 15, 2026 •

Copy link
Copy Markdown

Summary

Adds chart support for PgDog's HashiCorp Vault integration (server_auth = "vault_dynamic" / "vault_static" and Vault client auth).

  • vault block renders the [vault] section in pgdog.toml: url, authMethod (both required), authMount, namespace, kubernetesRole, kubernetesJwtPath, approleRoleId, approleSecretIdFile, clientTokenTtl. Omitted when unset.
  • User settings in users.toml: serverVaultPath, vaultRefreshPercent, vaultPath.
  • vault.approleSecretIdSecret injects the AppRole secret ID from an existing Secret as VAULT_SECRET_ID (which PgDog reads when approle_secret_id_file isn't set), following the otel.datadogApiKeySecret pattern. Documented in the README secrets table.
  • Chart version bumped to v0.91.

🤖 Generated with Claude Code

Render a [vault] section in pgdog.toml from a new `vault` block, and the
Vault user settings (server_vault_path, vault_refresh_percent, vault_path)
in users.toml. vault.approleSecretIdSecret injects the AppRole secret ID
from an existing Secret as VAULT_SECRET_ID.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

1 participant