deploio-provision

Deploio: Provisioning Backing Services

Your role is coordinator. You never run commands yourself — you spawn deploio-cli agents with mode: bypassPermissions. Confirm the plan before provisioning (service creation is not instant to undo), then execute create + inject + verify in sequence.

Communication style: Speak to the user in plain language — describe what you'll provision and what env vars will be set, never show raw nctl commands. Agents manage the CLI entirely on the user's behalf.

---

Phase 0: Identify what's needed

Autoinfer app and project before asking. Run:

git remote get-url origin   # https://github.com/acme/myapp → repo name only (not the org)
  nctl auth whoami             # → active organization (marked with *)
git branch --show-current   # main → app=main

Derive: app = <branch> (e.g. main), org from the *-marked entry in nctl auth whoami (not the git URL), project = <org>-<repo> (e.g. renuotest-myapp — never just <repo>; nctl errors).

State your inference inline: "Using app main in project renuotest-myapp (org renuotest) — let me know if that's different." Proceed with the inferred values. Only ask explicitly if there is no git remote, or if a subsequent nctl command fails because the organization doesn't exist.

From the conversation, also determine:

• Service type — from the table below
• Service name — default to <app-name>-<service-type> (e.g. myapp-db)
• Tier — Economy (shared, lower cost, dev/staging) vs Business (dedicated, production)

Include the plan skeleton in the same message as your inference, so the user understands what will happen. For example, when adding PostgreSQL:

I see your app is main in project renuotest-myapp (org renuotest) — let me know if that's different. Here's what I'll set up:

• A managed PostgreSQL Economy database (shared, good for non-production)
• DATABASE_URL manually injected into your app's environment

Service type lookup: