HashiCorp Vault
KV, transit and JWT auth. Jobs log in to Vault with their OIDC token.
At a glance
Section titled “At a glance”| Category | Secret managers |
| Authentication | Vault JWT/OIDC auth method (no static token) |
| Provider id | vault |
What it does
Section titled “What it does”- External secret references:
vault://... - Transit as the BYOK keyring
- Per-job short-lived Vault tokens
Set up
Section titled “Set up”- Grant the Slipway job identity (or the integration credential) read access to the secret path.
- In Settings, Integrations, add the secret manager.
- Create a Slipway secret of kind
external_refsuch asvault://kv/data/app#password. - Reference it as
${{ secrets.NAME }}inenvorwith.
Configuration
Section titled “Configuration”Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.
provider: vaultconfig: address: https://vault.example.com:8200 auth: jwt role: slipway-deploy mount: jwtSee OIDC with Vault.
Related
Section titled “Related”- Integrations overview
- Secrets for how credentials are stored and masked
- Webhooks and events for the events integrations subscribe to