Skip to main content

Screen: Environment

web/environment.html. A metadata-only view of the configuration registry: each application, the platforms it deploys to, the variables it needs, the providers behind them, and an audit log. Admin-only.

Names only, never values​

No secret values are held in this data and none are ever displayed. The page tells you a variable exists, whether it's required, who provides it, and whether it's set on each platform — never what it's set to. This is the same discipline the env-manifests/*.json files follow; see Env Manager Guide for the manifest format behind this screen.

What to actually use it for​

Checking whether a variable is configured on a platform before deploying, and finding which application owns a given piece of configuration — a lookup tool, not a secrets manager.

Where the code lives​

  • sable-agents-demo/web/environment.html
  • sable-agents-demo/web/api/environment.js, _environment.js — see the Admin, Environment, and Costs API
  • sable-agents-demo/scripts/env-manager/