apso deploy

Deploy the linked service to the Apso platform. Runs a local migration check before deploying to catch schema issues early.

Usage


apso deploy
apso deploy --yes
apso deploy --skip-migrate
apso deploy --no-wait
apso deploy --repo your-org/project-api --branch main

Option	Description	Default
`-y, --yes`	Skip confirmation prompt	`false`
`--skip-migrate`	Skip local migration validation	`false`
`--no-wait`	Trigger deploy without waiting for completion	`false`
`--skip-push`	Redeploy the source already connected to the service	`false`
`--repo <owner/name>`	Select a GitHub repository when none is connected	none
`--branch <name>`	Select the branch to push	`main`
`--local-git`	Push with local Git credentials instead of the platform connection	`false`

Verifies you are authenticated and the project is linked
Parses the current .apsorc schema
Runs the migration sandbox to validate schema changes (unless --skip-migrate)
If migrations are detected, shows the SQL and asks for confirmation (unless --yes)
If the migration fails locally, the deploy is blocked
Synchronizes local source to the connected GitHub repository unless --skip-push is set
Triggers the build on the platform
Polls for build completion and reports the result unless --no-wait is set

Deploy with all checks:


apso deploy

Deploy in CI (no prompts, no waiting):


apso deploy --yes --no-wait

Deploy without migration check:


apso deploy --skip-migrate

Connect a repository and use local Git credentials:


apso deploy --repo your-org/project-api --branch main --local-git

Must be authenticated (apso login)
Project must be linked to a platform service (apso link)
GitHub must be connected (apso github connect) unless the deployment uses source that is already synchronized