Skip to main content

Module deploy

Module deploy 

Source
Expand description

The app service: records on disk, the deploy queue and pipeline, and webhooks.

A deploy is a record (Deployment) that moves queued → building → deploying → done | failed. One runs at a time per app; a deploy asked for while one runs waits behind it, and a newer request supersedes a waiting one that has not started (superseded), so a burst of pushes builds the latest commit once.

The pipeline: resolve the image (an image source’s digest, or fetch the git source and build it with crate::build::run), render the app into its project environment’s stack in place of its old service, hand the stack to the controller, and wait for that service to converge.

Structs§

Apps
Projects, environments, apps and their deployments, for every org.
Commit
Deployment
One deploy of an app.

Enums§

Status
Trigger
Who asked for a deployment.

Type Aliases§

BuildFn
Turns a checkout into an image: crate::build::run, or a stand-in.
ImageProbe
Asks an image’s registry about it, waiting at most the given time: whether it exists, and its manifest digest (crate::image_check::probe, or a stand-in).
SecretHook
Called with an org and a secret’s name after it got a new value.