Using Context References

Overview

You can now insert dynamic references into property values when configuring environment properties or deployment properties.

These references automatically pull information from the current Deployment or Environment, so you don’t have to hard-code values.

When the deployment runs, the reference will be replaced with the actual value.

Available References

Deployment References

Reference	Description	Example Output
${{bricks.deployment.slug}}	The unique slug of the deployment.	payments-prod
${{bricks.deployment.package}}	The blueprint or package assigned to the deployment.	@bluebricks/payments_blueprint
${{bricks.deployment.created_time}}	The date/time the deployment was created. (Only works for existing deployments)	2025-06-30T09:27:14Z

${{bricks.deployment.created_time}} refers to the creation time of the parent deployment and not to a specific run. This means every run of the same deployment will have the same creation_time.

Environment References

Reference	Description	Example Output
${{bricks.env.slug}}	The unique slug of the environment.	prod
${{bricks.env.name}}	The display name of the environment.	Production

How It Works

Anywhere you can type a property value, you can use:

${{bricks.deployment.*}} → Information about the deployment

${{bricks.env.*}} → Information about the environment

When the deployment starts, these placeholders are replaced with the real values from your Bluebricks setup.

Example Usage

Environment Properties Page

You can set a property to dynamically reference the environment name:

app_env = ${{bricks.env.name}}

When deployed to Production environment, this becomes:

app_env = Production

Deployment Page

You can set a property to dynamically reference the environment name:

bucket_name = ${{bricks.deployment.slug}}

When deployed the property will be resolved as:

bucket_name = single-tenant-452846-service-bucket