pub struct VaultSettings {
pub address: String,
pub mount_path: Option<String>,
pub kv_secret_path_prefix: Option<String>,
pub jwt_role: Option<String>,
pub jwt_mount_path: Option<String>,
pub approle_role_id: Option<String>,
pub approle_mount_path: Option<String>,
pub namespace: Option<String>,
pub token: Option<String>,
pub skip_ssl_verify: Option<bool>,
}Fields§
§address: StringHashiCorp Vault server address (e.g., https://vault.company.com:8200)
mount_path: Option<String>KV v2 secrets engine mount path (e.g., windmill). Empty to test the connection used for $external:vault:// references, which checks only that Vault accepts Windmill’s token.
kv_secret_path_prefix: Option<String>Optional path prefix inserted between the KV data/metadata segment and the workspace id (e.g., "apps/windmill"). When set, secrets are stored at <mount>/data/<prefix>/<workspace>/<secret>, allowing a Vault policy scoped to exactly <mount>/data/<prefix>/_*.
jwt_role: Option<String>Vault JWT auth role name for Windmill (optional, if not provided token auth is used)
jwt_mount_path: Option<String>Mount path for the JWT auth method in Vault (optional, defaults to "jwt"). Set this when the JWT auth method is mounted at a non-default path, e.g. via vault auth enable -path=<mount> jwt.
approle_role_id: Option<String>AppRole role_id (optional). When set and no static token is given, Windmill logs in with AppRole; the secret_id is read from the VAULT_APPROLE_SECRET_ID environment variable of servers and workers.
approle_mount_path: Option<String>Mount path of the AppRole auth method (optional, defaults to "approle").
namespace: Option<String>Vault Enterprise namespace (optional)
token: Option<String>Static Vault token for testing/development (optional, if provided this is used instead of JWT authentication)
skip_ssl_verify: Option<bool>Skip TLS certificate verification when connecting to Vault. Only use for self-signed certificates in development environments.