edgible stack

Manage application stacks (declarative multi-app deployments)

edgible stack deploy

Deploy or update applications from a stack file

edgible stack deploy [flags]

Flag	Description
-f, --file <path>	Path to stack file (default: edgible.yml in current directory)
--app <name>	Deploy only specified application
--dry-run	Contact the API read-only to compute and print the deploy plan (create/update/in-sync/orphaned) without making changes
--skip-dependencies	Don’t deploy dependencies
--no-wait	Return after cutting the release without waiting for on-device convergence
--wait-timeout <seconds>	Max seconds to wait for convergence
--allow-hostname-removal	Acknowledge an apply that removes currently-routable hostnames (refused with HOSTNAME_REMOVAL_BLOCKED otherwise)
--json	Emit a single machine-readable JSON result (suppresses narration)

The --dry-run plan

--dry-run computes a real plan — it reads live state from the API (read-only, no changes) and prints one line per application, then a summary and the deploy order:

+ web       (create)
~ api       (update: 2 changes)
     spec.env.LOG_LEVEL: "info" → "debug"
     policies.ipRules.allow: array(1) → array(2)
= database  (in sync)
! legacy-cron (orphaned — not declared in this stack file; deploy will not touch it. Remove with: edgible stack teardown / application delete)

Plan: 1 to create, 1 to update, 1 in sync, 1 orphaned.

Marker	Meaning
+ create	Declared in the file but not yet live — deploy will create it.
~ update	Live and declared, but drifted — the path: from → to lines list what deploy will change.
= in sync	Live and matches the file — deploy makes no change.
! orphaned	Live in the org but not declared in this stack file. It may belong to another stack or an imperative application create. Deploy never touches an orphan — it is reported so you notice it, not scheduled for change.

Orphans are never deleted by a deploy. Removing an application is always explicit: edgible stack teardown for stack-managed apps, or edgible application delete for an individual one.

edgible stack teardown

Remove applications defined in a stack

edgible stack teardown [flags]

Flag	Description
-f, --file <path>	Path to stack file (default: edgible.yml in current directory)
--app <name>	Teardown only specified application
--force	Skip confirmation prompts
--keep-dependencies	Don’t teardown dependencies

edgible stack status

Check the status of applications in a stack

edgible stack status [flags]

Flag	Description
-f, --file <path>	Path to stack file (default: edgible.yml in current directory)
--json	Output as JSON
--app <name>	Show status for specific application

edgible stack validate

Validate a stack file without deploying

edgible stack validate [flags]

Flag	Description
-f, --file <path>	Path to stack file (default: edgible.yml in current directory)

edgible stack diff

Show differences between stack and deployed state

edgible stack diff [flags]

Flag	Description
-f, --file <path>	Path to stack file (default: edgible.yml in current directory)