Creating Deployments

Overview

A Deployment in Bluebricks represents the binding between a Blueprint and a target Environment.It defines what should be provisioned (the blueprint composition) and where it should be provisioned (the environment’s cloud accounts and configuration).

Deployments serve as the operational layer as they track the full lifecycle of infrastructure changes, from planning to applying, auditing, and teardown. Deployments lets members of your organization, spin-up, update, or uninstall infrastructure from your blueprints. This guide walks you through creating a deployment and understanding its possible statuses.

Deployment Runs

A deployment is the parent of all your runs. Each run represents an execution you perform within that deployment, such as a plan, apply, or destroy action. The deployment defines what you’re provisioning and where, while runs capture when and how those actions happen. Over time, your runs create a complete history of changes, making it easy for you to review, compare, or reapply past executions without redefining the blueprint or environment.

Creating a Deployment

You can create a deployment directly from the Deployments page in the Bluebricks web app or by using the CLI and API if you prefer automation. Once the deployment exists, each run within it can be initiated through multiple interfaces. You can trigger a run manually from the web UI, automatically through the API, or programmatically via webhooks or CI/CD pipelines. No matter how it starts, every run is fully tracked in the deployment’s history, keeping your execution flow consistent and auditable across all interfaces.