PAM

Config Files

Config Files store entire application configuration artifacts -- YAML, JSON, TOML, properties, or arbitrary text -- alongside the secrets they reference. Each file is encrypted at rest with the workspace KEK, versioned on every save, and retrievable via API, CLI, or SDK. Embedded secret references ({{secret.name}}) are resolved at retrieval time so the deployed file always contains the current rotated values.

Version history keeps every prior revision with diff view, and rollback restores a previous version as a new head. Files are scoped to workspace and environment so a single template can be deployed with environment-specific substitutions.

Config Files screenshot

Key Configuration

  • File format (YAML, JSON, TOML, properties, raw)
  • Embedded secret reference syntax
  • Version retention policy
  • Environment-specific overrides
All documentation Question about this? Talk to us