# Orchestration - [Orchestration Overview](https://bluebricks.co/docs/orchestration/orchestration.md): Manage infrastructure through the Bluebricks platform UI and CLI with governed deployment pipelines. - [Orchestration Quick Start](https://bluebricks.co/docs/orchestration/orchestration-quick-start.md): Create your first collection, blueprint, and environment using the Bluebricks orchestration platform. - [Collections](https://bluebricks.co/docs/orchestration/collections.md): A collection is a logical unit for provisioning cloud infrastructure - [Creating Collections](https://bluebricks.co/docs/orchestration/collections/create-an-environment.md): Create collections from the Bluebricks app or CLI to organize infrastructure by team, project, or lifecycle stage - [Managing Collections](https://bluebricks.co/docs/orchestration/collections/managing-collections.md): List, enable, disable, and delete collections using the Bluebricks app or the Bricks CLI - [Owners and Members](https://bluebricks.co/docs/orchestration/collections/owners-and-members.md): Control who can access and govern your collections by assigning owners and members - [Properties](https://bluebricks.co/docs/orchestration/collections/properties.md): Adapt reusable blueprints to a specific collection with key-value properties - [Secrets](https://bluebricks.co/docs/orchestration/collections/secrets.md): Store and manage sensitive values like API keys and credentials at the collection level - [Policies](https://bluebricks.co/docs/orchestration/collections/policies.md): Define approval workflows, cost limits, and allowed blueprints to govern how environments operate within a collection - [Packages](https://bluebricks.co/docs/orchestration/packages.md): Packages are the reusable building blocks of Bluebricks - [Blueprints](https://bluebricks.co/docs/orchestration/packages/blueprints-overview.md): Blueprints are reusable templates that compose infrastructure stacks - [Creating Blueprints](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/creating-blueprints.md): Combine multiple packages into a reusable, deployable infrastructure blueprint - [From Code to Blueprint](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/from-code-to-blueprint.md): Turn existing Infrastructure as Code into a reusable Bluebricks blueprint you can deploy, version, and share across teams - [Using expr](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/expr.md): Use the expr expression language in bricks.json for dynamic configuration, conditional logic, string operations, and runtime property references - [Blueprint Composition Patterns](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/blueprint-composition-patterns.md): Common patterns for composing blueprints, managing package dependencies, and structuring outputs effectively - [Local Development](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/local-development.md): Test and iterate on blueprints locally using bricks run before deploying to cloud environments - [Publish with bricks.yaml](https://bluebricks.co/docs/orchestration/packages/blueprints-overview/publish-with-bricks-yaml.md): Publish blueprints using bricks.yaml for simplified syntax, auto-populated fields, multi-document support, and YAML-native features - [Artifacts](https://bluebricks.co/docs/orchestration/packages/artifacts-overview.md): Artifacts wrap your existing IaC code into versioned, reusable building blocks - [Creating Artifacts via CLI](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/creating-artifacts.md): Create reusable Infrastructure as Code artifacts in Bluebricks to standardize infrastructure and enable consistent deployments across environments - [Terraform/OpenTofu](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/terraform-open-tofu.md): Terraform and OpenTofu: understand managed state, input/output, and versioned rollouts - [Publish a Terraform Module](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/terraform-open-tofu/publish-terraform-module.md): Convert an existing Terraform module into a Bluebricks package using the prepare and publish CLI workflow - [Helm](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/helm.md): Helm reference: chart lifecycle, Kubernetes authentication, release tracking, and input/output - [CRD Management](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/helm/helm-crd-management.md): How Bluebricks automatically handles Custom Resource Definitions (CRDs) in Helm charts using server-side apply for reliable, consistent deployments - [CloudFormation](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/cloudformation.md): CloudFormation reference: parameter mapping, outputs capture, and AWS authentication - [Generic](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/generic.md): Generic artifact reference: run any containerized task as a one-shot Kubernetes Job - [Container Configuration](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/generic/container-config.md): Configure Docker containers for Generic artifacts: image selection, commands, environment variables, and approved registries - [Lifecycle and Execution](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/generic/lifecycle.md): How Generic artifacts execute across deployment stages, with per-stage configuration and smart execution caching - [Bicep](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/bicep.md): Bicep reference: deployment modes, parameter mapping, outputs capture, and Azure authentication - [Deployment Modes](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/bicep/bicep-deployment-modes.md): Choose between Complete and Incremental deployment modes for Bicep artifacts based on resource group ownership - [.bricksignore](https://bluebricks.co/docs/orchestration/packages/artifacts-overview/.bricksignore.md): Exclude large or unnecessary files from published packages using a .bricksignore file, similar to .gitignore pattern format. - [Inputs & Outputs](https://bluebricks.co/docs/orchestration/packages/inputs-and-outputs.md): How inputs and outputs define the interface of every package in Bluebricks - [Environments](https://bluebricks.co/docs/orchestration/environments.md): An environment is the workflow that provisions, updates, and destroys infrastructure by executing a blueprint against a target collection - [Creating Environments](https://bluebricks.co/docs/orchestration/environments/creating-environments.md): Create environments from the Bluebricks app or CLI to deploy blueprints into collections - [GitOps Environments](https://bluebricks.co/docs/orchestration/environments/gitops-environments.md): Automatically trigger infrastructure plans and deployments from Git pushes - [Archiving Environments](https://bluebricks.co/docs/orchestration/environments/archiving-environments.md): Remove environments from your active list without affecting deployed infrastructure - [Automatic Drift Detection](https://bluebricks.co/docs/orchestration/environments/drift-detection.md): Detect when infrastructure state diverges from the desired blueprint configuration - [Time to Live (TTL)](https://bluebricks.co/docs/orchestration/environments/environment-ttl.md): Define how long an environment should be up and running - [Runs](https://bluebricks.co/docs/orchestration/runs.md): Plan and apply infrastructure changes through runs - [Monitoring Runs](https://bluebricks.co/docs/orchestration/runs/monitoring-runs.md): Track run progress and status from the Bluebricks app or CLI - [Destroying Environments](https://bluebricks.co/docs/orchestration/runs/destroying-environments.md): Uninstall an environment to destroy all infrastructure resources it provisioned - [Promoting Environments](https://bluebricks.co/docs/orchestration/runs/promoting-environments.md): Promote an environment run to another collection with the same blueprint and inputs - [State Management and History](https://bluebricks.co/docs/orchestration/runs/state-management-and-history.md): Track infrastructure state safely across environments and teams - [Environment Manifest File Format](https://bluebricks.co/docs/orchestration/runs/deployment-manifest-file-format.md): Declarative YAML format for defining environment state, used in CI/CD pipelines and Git-based infrastructure workflows - [Using Outputs References](https://bluebricks.co/docs/orchestration/runs/using-outputs-references.md): Use the outputs of one environment as inputs for another to compose modular, cross-layer infrastructure architectures - [Using Context References](https://bluebricks.co/docs/orchestration/runs/using-context-references.md): Insert dynamic references to environment and collection metadata in property values, resolved automatically at runtime - [Parallel Execution](https://bluebricks.co/docs/orchestration/runs/parallel-execution.md): How Bluebricks executes blueprint packages in parallel based on their dependencies - [Cloud Graph](https://bluebricks.co/docs/orchestration/cloud-graph.md): Get a comprehensive understanding of the cloud graph - [Webhooks](https://bluebricks.co/docs/orchestration/webhooks.md): Configure webhook callbacks to receive real-time notifications for environment events like creation, updates, and status changes - [Best Practices](https://bluebricks.co/docs/orchestration/bluebricks-git-repository-guide.md): Best practices for using Git repositories as the primary driver for infrastructure modifications with Bluebricks - [Git Repository Folder Structure](https://bluebricks.co/docs/orchestration/bluebricks-git-repository-guide/git-repository-folder-structure.md): Recommended folder structure for managing Bluebricks artifacts, blueprints, and environment configurations in a Git repository - [Getting Started with Bricks Action](https://bluebricks.co/docs/orchestration/bluebricks-git-repository-guide/getting-started-with-bricks-action.md): Set up the Bricks GitHub Action to run CLI commands in GitHub workflows for automated version bumping, publishing, and deployment - [Managing Infrastructure-as-Code on Git](https://bluebricks.co/docs/orchestration/bluebricks-git-repository-guide/managing-infrastructure-as-code-on-git.md): Automate blueprint version bumping, publishing, and updates through Git-based CI workflows using Bricks Action - [Managing Configuration on Git](https://bluebricks.co/docs/orchestration/bluebricks-git-repository-guide/managing-configuration-on-git.md): Use declarative environment files and PR-based workflows to manage infrastructure provisioning through Git with Bricks Action --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bluebricks.co/docs/orchestration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.