Alis Build DBD¶
Alis Build DBD is Define, Build, Deploy: the three steps every change to a service goes through, each from a pushed commit. Define compiles a service's protobuf contract into versioned packages, Build turns a pushed commit into an immutable version, and Deploy applies the service's Terraform into a deployment environment, with a person's approval before production. This page lists where DBD shows in the console, the commands that run it, and the reference pages for its details.
In the console¶
Versions and deploys show on the screens of Alis Build Environments:
- a product's Services lists every service with its version in each deployment environment, and deploys or destroys one;
- a product's and a deployment environment's Variables save variables with Save and Deploy or Plan Deploy;
- a deployment environment's Overview lists the services deployed there now;
- a product's Reference is the API reference of its defined packages.
A contract version's Glass view shows every artifact of that version as it lands. Open it with the Glass view button in the version's title bar.
| Glass view | Path |
|---|---|
| A contract version | /build/environments/<org>/products/<product>/reference/packages/<packageId>/versions/<version>/glass |
From the CLI¶
| Command | Purpose |
|---|---|
alis define |
Define a service's protos into a new version |
alis build |
Build a service into a new version |
alis deploy |
Deploy a service version to a deployment environment |
alis packages |
Install, upgrade and add a service's packages |
alis operations |
Inspect and wait on long-running operations |
alis logs |
Read build, deployment, and Cloud Run runtime logs |
Details¶
- Package ids and folders: how a package id maps to a resource, a build folder and a define folder, and how the CLI resolves context from the working directory.
- Dockerfile detection: which files become images, how images are named and the flags that select them.
- Terraform variables: every
ALIS_*variable injected into a service's Terraform, and the image reference format. - Operations and output: the JSON of long-running operations, error envelopes, stderr events and exit codes.