nodejs config BSB v9.6.59

config-vault

bsb/config-vault

Managed BSB config plugin that loads latest active config from Vault

vault config managed runtime

config-vault

config-vault is a BSB config plugin that loads runtime config from Vault.

Only one BSB config plugin can be active. If BSB_CONFIG_PLUGIN=config-vault, Vault owns the full runtime config source.

Runtime Behavior

config-vault is activated as the BSB config source with environment variables, not as a normal plugin config block in sec-config.yaml.

BSB_CONFIG_PLUGIN=config-vault
BSB_CONFIG_PLUGIN_PACKAGE=@bsb/config-vault
vaultUrl=https://vault.example.com
apiKeyId=vk_xxx
apiSecret=vs_xxx
timeoutMs=5000

The lower camel case keys are intentional. BSB reads config plugin env vars from the plugin schema, so vaultUrl, apiKeyId, apiSecret, timeoutMs, and allowInsecureHttp are the exact keys used by this plugin.

The API key is bound in Vault to:

  • application,
  • service group,
  • deployment profile,
  • optional container name,
  • allowed config plugin id.

The container cannot ask for another profile. Vault derives the target from the API key and returns the latest active published version.

Failures

Startup fails if:

  • Vault is unreachable,
  • authentication fails,
  • vaultUrl is not HTTPS and allowInsecureHttp is not enabled,
  • no active version exists,
  • Vault returns invalid config,
  • the selected profile has no enabled service plugins.

There is no fallback chain to config-env or config-default.

Installation

Install plugin (Node.js)
npm i @bsb/config-vault

Configuration

Configuration for config plugins is provided through environment variables:

No configuration required

Available Versions

v9.6.59 v9.6.58 v9.6.57 v9.6.56 v9.6.55 v9.6.54 v9.6.53 v9.6.52 v9.6.51 v9.6.50 v9.6.49 v9.6.48 v9.6.47 v9.6.46 v9.6.45 v9.6.44 v9.6.43 v9.6.42 v9.6.41 v9.6.40 v9.6.39 v9.6.38 v9.6.37 v9.6.36 v9.6.35 v9.6.34 v9.6.33

Metadata