Runtime configuration surfaces
Select a supported UI, API, Helm, or repository configuration surface and verify each change.
Different surfaces own Lifecycle configuration. Select the surface that owns the value that you want to change. Use only a documented configuration surface.
Configuration map
| What you are changing | Supported surface |
|---|---|
| Application Services, builds, deployments, and Environment defaults | Repository lifecycle.yaml |
| Personal API keys | API keys in Settings |
| User connections | External MCP connections in Settings |
| Lifecycle MCP enablement and change-tool policy | Platform administration → Lifecycle MCP |
| API key policy and service keys | Settings → API key management or its typed v2 API |
| PR-less Environment policy | Settings or the typed API Environment policy endpoint |
| Sites limits and availability | Settings → Sites or its typed v2 config endpoint |
| Agent models, instructions, tools, workspaces, and session review | Admin Agent sections in Settings |
| Environment metadata links | Authenticated v2 metadata configuration API |
| Component replicas, resources, ingress, dependencies, and pod settings | Versioned Helm values |
| Infrastructure, DNS, and evaluation cluster resources | The selected installation and infrastructure workflow |
If the map does not contain your setting, do not change the value through an undocumented method. Ask your deployment owner for a versioned procedure.
Configuration change procedure
For a supported change:
- Record the previous value without recording secrets.
- Make the smallest change through the owning surface.
- If the feature requires a restart or propagation procedure, apply it.
- Make sure that one affected task operates correctly.
- If the task does not operate correctly, apply the previous value through the same surface.
Do not restart all components unless the applicable procedure tells you to do so.
Secret handling
Keep credentials in Kubernetes Secrets, an external secret provider, or the
approved credential UI or API for the feature. Do not put plaintext tokens in
Helm history, screenshots, issue text, lifecycle.yaml, or diagnostic commands.