The lifecycle of a deployment determines its readiness to accept user requests and serve traffic.
From an API standpoint, each deployment has a
readyState field which can take one of the following values:
INITIALIZINGa deployment in this state is waiting on builds to complete
ERRORone or more builds failed
READYbuilds completed successfully or none were specified
An illustration of the deployment
When a deployment is
READY, our system guarantees that it can be served at any time and that all the underlying serverless functions are available in the specified regions.
No further state transitions are necessary, and all deployment entrypoints are expected to be served within milliseconds.
When a deployment has more than one underlying builds, each build has its own states and lifecycle.
Now CLI displays and updates the evolution of the builds' states until the deployment completes.
An illustration of a build's lifecycle.
Each build process goes through:
INITIALIZINGthe initial state
ANALYZINGto determine if the build has to be performed or it can be de-duplicated
BUILDINGwhile executing the Builder code
UPLOADINGto upload the files and resulting lambdas
DEPLOYINGto deploy the necessary files and functions
READYif the deployment is successful
ERRORif the deployment fails
ERRORif an upload fails
ERRORif an error occurs during the build code executions
READYif no build is necessary
ERRORif an error occurs during the analysis code execution