app_up
Plan or execute the canonical app deployment workflow from a local path or Git repository, returning graph steps, resources, and diagnostics.
Instructions
Plan or run the canonical app-aware run402 up workflow from a local path or repo URL. Delegates to the SDK and returns the shared app-up result envelope with graph steps, resources, diagnostics, and next_actions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dir | No | Workspace directory to inspect when source is omitted. | |
| yes | No | Approve non-interactive prerequisite, spend, and local-write prompts. | |
| name | No | Project/app instance name, for example kysigned2. | |
| tier | No | Bootstrap tier if account readiness is needed. | |
| source | No | Local app directory or public Git repository URL. Defaults to the current directory. | |
| dry_run | No | Plan only. No gateway mutation, build execution, release commit, local link write, or prune. | |
| manifest | No | Explicit manifest path. Defaults to run402.json, then advanced release-only manifests. | |
| build_mode | No | Override app build mode. | |
| project_id | No | Existing project id to install into. | |
| allow_prune | No | Approve destructive managed-resource prune steps. | |
| max_spend_usd | No | Maximum spend app_up may approve for readiness steps. | |
| idempotency_key | No | Root idempotency key for resumable app-up graph mutations. | |
| allow_shell_build | No | Approve shell-string build commands after review. |