Properties

Shape your blueprints with environment-specific properties

Overview

Environment properties let you adapt reusable blueprints to the context of a specific environment. Think of properties as the “color” you apply to a blueprint: they supply values such as regions, naming conventions, or account-specific defaults. By setting these at the environment level, you ensure that every deployment automatically inherits the right configuration without requiring the deployers to redefine it each time.

How Environment Properties Work

When a blueprint property key matches an environment property name, the environment’s value is injected automaticallyOnce defined, environment properties automatically apply to every deployment in that environment. They align blueprint inputs with the values you set, so you don’t need to redefine them for each run.

• Environment properties override defaults defined in the blueprint, ensuring consistent values across deployments.

• If a property is marked as enforced, deployments must use that exact value. This is useful for governance (e.g., forcing all resources into eu-west-1).

• Properties can reference dynamic values like environment slug or deployment metadata (e.g., ${{bricks.env.slug}}_${{bricks.deployment.id}}).

Enforced properties are hard-coded values; if not enforced, they act as defaults that deployments can override.

Setting properties

To set environment-level properties:

1. Navigate to the desired environment page

2. Select "Properties" from the left side menu

3. Click "Add property"

4. Enter name (Key) & value

5. (Optional) Mark whether to enforce that property

6. Click "Save"