Skip to main content
wiring/tenant-connector-vault
check: wiring/tenant-connector-vault · error_code: E-TENANT-001 · doctor exits: 0

​
What you’re seeing

A warning: your source reaches vendo.tenantConnectors, and neither VENDO_STORE_ENCRYPTION_KEY nor VENDO_API_KEY is set.

​
Why

Tenant connectors vault the token a customer pastes in the store’s encrypted secrets. The store keeps a secret encrypted or not at all: without a key, a development write lands in the clear (with its own loud warning), and a production write is refused outright. So this is a deploy-shaped failure, not a local one. Every registration you make on your laptop works, and the first one you make in production comes back an error the moment it carries a token.

​
The fix

Set one of two names.
Or use Vendo Cloud’s hosted store, which holds the key server-side:
A warning, not a failure: production-only env kept outside the files doctor can read is legitimate. If that is your setup, verify with a real vendo.tenantConnectors.register call in the environment where the key exists.

​
What this check does not do

Doctor reads what is on disk. It never opens your store, so it does not read your registration rows, and it never dials a tenant’s server. Checking that one tenant’s connector still answers is vendo.tenantConnectors.test(org, name), at runtime, where a live handshake belongs.
  • E-STORE-001 — the other way a store loses data an operator assumed was kept
  • E-CLOUD-001 — a VENDO_API_KEY that is set but not usable