Manifest reference¶
mithran.yaml is the committed app contract. This page describes the fields that the portal can document without inventing hosted behavior.
Contract shape¶
| Field | Meaning |
|---|---|
| API version | Identifies the manifest schema accepted by the deployed parser. |
| Runtime | Identifies how the app starts and which port it serves. |
| Exposure | Declares the app's intended reachability boundary. |
Use the exact schema accepted by the installed Aegis distribution. Keep values that affect runtime behavior in the repository so a commit describes one reproducible app.
Source and identity¶
The manifest does not choose environment, tenant, account, installation, or app identity. Authorization and repository context derive those values. Automation can choose only repository, ref, or commit.
Do not store credentials, private keys, or other secrets in the manifest. Use the operator's approved secret channel when the runtime requires a secret.
Review¶
Review the manifest with the source and Dockerfile. Commit the reviewed files before deployment, then record the commit selected by the deployment request.