Profiles
Quick Answer
This is an advanced/internal model guide. Canonical end-user lifecycle language is pull, push, validate, and run (with release/promote/installations as advanced rollout operations).
Why This Exists
The backend runtime uses profile objects internally to store:
- resolved bindings for
:requires - activation/config inputs
- enabled state and version pinning
Most users should use installation commands instead of profile terminology.
Canonical Mapping
| Internal profile concept | Canonical user concept |
|---|---|
| Prod profile | Live installation target |
| Installation profile | End-user installation target |
| Draft target profile | Default run target |
CLI Context vs Internal Profiles
- CLI
--profileselects CLI client config (API URL/token/workspace). - Internal profile ids are runtime identifiers used behind installation/run resolution.
When You Need This Page
Use this page only when debugging low-level behavior, migrations, or API internals that expose profileId.