Using Context References
Insert dynamic references to environment and collection metadata in property values, resolved automatically at runtime
Last updated
Insert dynamic references to environment and collection metadata in property values, resolved automatically at runtime
You can insert dynamic references into property values when configuring collection properties or environment properties.
These references automatically pull information from the current Environment or Collection, so you don’t have to hard-code values.
When the environment runs, the reference will be replaced with the actual value.
${{bricks.environment.slug}}
The unique slug of the environment.
payments-prod
${{bricks.environment.package}}
The blueprint or package assigned to the environment.
@bluebricks/payments_blueprint
${{bricks.environment.created_time}}
The date/time the environment was created. (Only works for existing environments)
2025-06-30T09:27:14Z
${{bricks.environment.created_time}} refers to the creation time of the parent environment and not to a specific run. This means every run of the same environment will have the same creation_time.
${{bricks.collection.slug}}
The unique slug of the collection.
prod
${{bricks.collection.name}}
The display name of the collection.
Production
Anywhere you can type a property value, you can use:
When the environment starts, these placeholders are replaced with the real values from your Bluebricks setup.
You can set a property to dynamically reference the collection name:

When deployed to Production collection, this becomes:
You can set a property to dynamically reference the environment name:

When deployed the property will be resolved as:
Last updated
${{bricks.environment.*}} → Information about the environment
${{bricks.collection.*}} → Information about the collectionapp_collection = ${{bricks.collection.name}}app_collection = Productionbucket_name = ${{bricks.environment.slug}}bucket_name = single-tenant-452846-service-bucket