Deploy, start, stop and delete an app

These actions are in the header of the app's page and need apps/write; deleting needs apps/delete. The Owner, Contributor and Apps Operator roles have both. The toast that follows an action means the platform accepted it; the status next to the app's name shows how it goes — see Statuses.

Deploy

Choose Deploy — Re-deploy while the app runs:

• An app built from a repository is built again and the new image rolled out. The build uses the commit the app is on: the last commit a push to its branch delivered, or the latest commit on the branch when no push has been recorded. After Redeploy this version rebuilt an older commit, the app stays on that commit until the next push to its branch.
• An app that runs a container image gets new instances, which pull the image again — the way to pick up a tag that was pushed again.

A deploy to a stopped app builds the new version but serves nothing until you start the app. The build and its log are on the Deployments tab — see Deployments and revisions.

Start, stop and restart

• Stop takes the app down to zero instances. It remembers the scaling it had, autoscaling included; the app shows Stopped.
• Start brings back the scaling the app had when it was stopped.
• Restart replaces the app's instances with new ones on the same image; nothing is rebuilt. An app without persistent storage keeps serving while its instances are replaced one at a time; an app with persistent storage is down briefly, because the old instance has to release the disk before the new one starts. Restarting a stopped app starts it.

While the app is in Error, the header offers only Deploy.

Changing the app's configuration never starts or stops it: a stopped app stays stopped.

Open the app

Browse opens the app in a new tab. It is there while the app is Running or Degraded; with several served domains it lists them, primary first.

Delete an app

Open the app's Danger Zone tab, choose Delete, and type the app's name to confirm. The app is removed with its slots, their persistent disks and the app's managed identity. Deleting cannot be undone.

With the CLI

stsh works in the resource group you give with -g (or the one your context names):

stsh apps list -g my-resource-group
stsh apps get my-app -g my-resource-group
stsh apps deploy my-app -g my-resource-group
stsh apps stop my-app -g my-resource-group
stsh apps start my-app -g my-resource-group
stsh apps restart my-app -g my-resource-group
stsh apps delete my-app -g my-resource-group

stsh apps list -A lists the apps of every resource group in the boundary. The commands that change something wait for the platform's operation to finish and report how it ended; --no-wait returns as soon as the request is accepted. delete asks you to confirm; --yes skips the question. stsh apps pods my-app lists the app's running instances.