Environments

Overview

A Bluebricks Environment is a logical unit for provisioning and managing cloud infrastructure. An environment can be tied to a specific cloud provider account, region, or an on-premises target, and member access is controlled via RBAC so permissions remain clear and auditable. You can attach properties and secrets to an environment; those values are automatically inherited by any package deployed to that environment, keeping packages reusable while allowing them to adapt to their deployment context.

Environments organize infrastructure into clear units that map to how teams actually work — for example, projects, teams, or lifecycle stages such as development, staging, and production. Each environment serves as the foundation for deployments by holding shared settings, credentials, and governance rules that determine where and under which policies blueprints are executed.

What an Environment Contains

An Environment is more than a label — it bundles the practical pieces Bluebricks needs to operate safely and predictably:

• Target configuration — cloud account and any contextual identifiers that determine where resources are created.

• Policy surface — the set of Environment Policies (approvals, cost limits, allowed blueprints, etc.) that govern what runs and how.

• Variables & secrets — environment-scoped inputs, secret references, and parameter defaults that deployments consume.

• RBAC & access controls — who may create, edit, approve, or execute deployments in the environment.

This bundle ensures that every deployment targeted at an Environment follows consistent operational rules and can be audited, repeated, and governed.

Best Practices

• Name and scope environments clearly (e.g., dev-us-east-1, staging, prod-eu) so teams and automation can target them unambiguously.

• Segment sensitive workloads into dedicated environments or accounts to enforce strict security boundaries.

• Use environment policies to protect production and apply cost controls in shared environments.

• Keep environment variables minimal and explicit—treat them as the contract for deployments.