Create a Blueprint

Create blueprints by composing multiple packages into complete infrastructure solutions.

For a full conceptual overview of blueprints -- including the web UI wizard, inputs, outputs, and source-based packages -- see Creating Blueprints in the docs. You can also browse published blueprints in the catalog.

Prerequisites

• Bluebricks CLI installed

• Authenticated (bricks login)

• Existing packages to compose

Quick Start (CLI)

1. Initialize a blueprint:

   bricks blueprint init

2. Add packages:

   bricks blueprint add @bluebricks/terraform_aws_vpc
   bricks blueprint add @bluebricks/terraform_aws_subnet

3. Configure dependencies by editing bricks.json -- use Data.* references to wire package outputs to inputs.

4. Publish the blueprint:

   bricks blueprint publish

Key CLI Commands

# Add / remove packages
bricks blueprint add @bluebricks/terraform_aws_vpc@1.2.0
bricks blueprint remove @bluebricks/terraform_aws_vpc

# Inspect blueprint
bricks blueprint describe

# Update packages
bricks blueprint update --all
bricks blueprint update --all --patch

# Version bump and publish
bricks blueprint bump --patch
bricks blueprint publish

Dependency Resolution

Bluebricks uses implicit dependencies through Data.* references to build a DAG of package execution order.

{
  "packages": [
    { "name": "@bluebricks/terraform_aws_vpc", "id": "vpc_main" },
    {
      "name": "@bluebricks/terraform_aws_subnet",
      "id": "subnet_web",
      "props": {
        "vpc_id": { "value": "Data.vpc_main.vpc_id" }
      }
    }
  ]
}

The Data.vpc_main.vpc_id reference means subnet_web depends on vpc_main. Bluebricks executes vpc_main first, then subnet_web.

See also

• Creating Blueprints -- full walkthrough with the web UI wizard

• How to Publish Blueprints with bricks.yaml -- simplified YAML-based publishing

• How to Publish Blueprints with CLI -- CLI publishing details

• Blueprint Composition Patterns -- advanced composition techniques