How can we help you?

GitBook Assistant

Browse by topic

chevron-rightAuthentication Login issues, expired tokens, and API keyshashtag
chevron-rightDeployments & runs Stuck runs, approval blocks, environment errors, and slug conflictshashtag
chevron-rightPackages & blueprints Publishing errors, invalid references, and validation failureshashtag
chevron-rightCloud connections AWS, Azure, GCP, and self-hosted connection problemshashtag
chevron-rightSelf-hosted runner OOMKilled jobs, stuck tasks, storage and Helm issueshashtag
chevron-rightOperational guides Terraform local development, state migration, and other one-time procedureshashtag

FAQs

chevron-rightWhat is the difference between an artifact and a blueprint?hashtag

An artifact is a single Infrastructure as Code (IaC) component: one Terraform module, one Helm chart, one CloudFormation template, one Bicep template, or one generic container. Artifacts are not directly deployable.

A blueprint is a deployable unit composed of one or more packages (artifacts or other blueprints). Blueprints define relationships between packages, wire inputs and outputs, and expose an interface to the deployer.

For the full explanation, see Packagesarrow-up-right.

chevron-rightWhat is the difference between a collection and an environment?hashtag

A collection is the target: it groups a cloud account, RBAC rules, properties, secrets, and policies into a single unit.

An environment is the workflow that deploys a blueprint to a collection. Each environment execution creates a run.

For details, see Collectionsarrow-up-right and Environmentsarrow-up-right.

chevron-rightWhat IaC tools does Bluebricks support?hashtag

Bluebricks supports five artifact types:

  • Terraform and OpenTofu (with version control and state management)

  • Helm (Kubernetes package manager)

  • CloudFormation (AWS native)

  • Bicep (Azure native)

  • Generic (any containerized workflow)

See the Artifacts Overviewarrow-up-right for details on each type.

chevron-rightHow do I enable pre-release versions?hashtag

Pre-release package versions are disabled by default. Your organization admin can enable them in the organization settings. Once enabled, pre-release versions appear alongside stable versions when installing blueprints.

chevron-rightHow do I check my CLI version and authentication status?hashtag

Run these two commands:

bricks --version shows the installed CLI version. bricks whoami confirms your current authentication status and user ID.

chevron-rightCan I use Bluebricks without Kubernetes?hashtag

Yes. Kubernetes is only required if you use the self-hosted runner (BDC) to execute deployments in your own infrastructure. Bluebricks also offers a managed runner option that does not require a Kubernetes cluster.

If you do need a lightweight Kubernetes setup, see Orchestrator in a Boxarrow-up-right for deploying K3s on a single VM.

chevron-rightHow do I connect multiple cloud accounts?hashtag

Each collection connects to one cloud account. To manage multiple cloud accounts, create separate collections for each account. You can deploy the same blueprint across multiple collections, each targeting a different cloud account.

For setup instructions, see Connect your Cloudarrow-up-right.

chevron-rightWhat are the network requirements for the self-hosted runner?hashtag

The Bluebricks Deployments Controller (BDC) requires outbound HTTPS access (port 443) to:

  • api.bluebricks.co (Bluebricks API)

  • ghcr.io (container images)

  • europe-docker.pkg.dev (Helm chart registry)

  • Your cloud provider APIs (AWS, GCP, Azure)

No inbound ports need to be opened. For the full list of requirements, see Network Requirementsarrow-up-right.