Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deploy and promote across environments

The operational path from a dev Tenant to production.

Deploying is one thing; promoting a product from experimentation to production reliably is the operational discipline around it. How you promote depends on how your Operator sliced Tenants (see Tenants and blueprints).

How the deploy works

The mechanics live in Build. You generate a deploy.yaml, apply it, and verify the product is live. This page assumes that and focuses on the promotion path. For the deploy steps themselves, see Git & deploy in the Build guide.

Promote with environment Tenants

The common blueprint separates environments into their own Tenants (dev, stg, prod). Promotion is then a controlled progression of the same project across Tenants:

  1. Build and validate in dev. Plan and run locally, then deploy to the dev Tenant. Confirm runs, quality checks, and the served APIs behave.

  2. Promote to staging by deploying the same Git ref to the staging Tenant, pointed at staging data sources and Compute. Validate against production-like data and access.

  3. Promote to production by deploying the same ref to the prod Tenant. Production is the source of truth; nothing reaches it that did not pass staging.

What changes between environments is configuration, not code: the Tenant, the Depots and Compute it points at, and the Secrets that hold data source credentials, all resolved per Tenant. Keep the project identical and let the environment supply the connections.

Operating practices

  • One source of truth. Promote a specific, tagged Git ref forward; do not edit directly in a higher environment.

  • Same project, different config. Parameterize connections so the same code runs in each Tenant; never fork per environment.

  • Promote on green. A product moves up only when its plan, tests, and quality checks pass in the environment below.

  • Coordinate breaking changes. A schema or grain change that reaches production affects consumers; sequence it with the guidance in Monitor Data Product.

  • Update in place. To ship a change to a deployed Data Product, re-apply it with --re-run instead of deleting and redeploying, which takes its API down for consumers. See Update a deployed Data Product.

  • Record what is where. Track which ref is deployed in each Tenant so you can reason about and roll back a release.

Once deployed, the job becomes keeping it healthy: Monitor Data Product.

Last updated

Was this helpful?