October 2025

Bluebricks Release Notes

Deploy with Confidence

This release introduces a brand-new Deployment experience, complete with automatic drift detection and richer blueprint controls. We’ve also tightened reliability, observability, and performance across state handling, executors, and deployment flows—so managing infrastructure day to day feels clearer and safer.

🚀 New Features

New Deployment Page & Enhanced Table Views

We’ve launched a dedicated Deployment Page with focused tabs for overview and drift detection, a detailed runs view, and contextual action menus right where you need them.

What it means for you: You get a single, comprehensive view of each deployment—its status, history, drift state, and next actions—making it easier to investigate issues, approve changes, and follow the full lifecycle of your infrastructure.


Automatic Drift Detection

You can now enable automatic drift detection per deployment. By default, drift checks run every 24 hours at 2:00 AM UTC, and any deployment with detected drift is clearly marked.

What it means for you: Drift becomes a first-class signal instead of a hidden risk. You’ll know when real-world infrastructure diverges from your declared state and can act before it causes incidents.


Blueprint Wizard: Allowed Values

The Blueprint Wizard now supports dropdown-style allowed values for properties, letting you define a curated list of valid options for each input.

What it means for you: Consumers of your blueprints get a guided, form-like experience with fewer mistakes—inputs are easier to fill and harder to misconfigure.


⚡ Improvements

Auto-enriched Bicep artifacts with resource group

During Bicep artifact publishing, artifacts are now automatically enriched with a resourceGroup property (similar to location), improving consistency and simplifying parameter wiring.

On-demand metrics initialization via internal API

Metrics bootstrap has been moved to an internal API endpoint, allowing metrics to be initialized explicitly rather than automatically at startup, giving you finer control over monitoring behavior.

Non-blocking S3 tagging for state locks

Tagging S3 lock files no longer blocks deployments. Tagging failures are logged as warnings instead of causing runs to fail, improving robustness in noisy or constrained storage environments.

Automatic ownership for environment creators

When you create or clone an environment, you’re automatically listed as its owner, ensuring clear accountability and easier permission management from day one.

Redis memory usage alerts at 80% and 90%

We’ve added proactive Coralogix alerts for Redis usage: a warning at 80% and a critical alert at 90%, helping catch memory issues before they impact service stability.

Upload Deployment States API

A new API endpoint supports uploading state files to draft deployments, making migrations and state restoration workflows smoother and more controlled.

Consistent state tracking via State API

The State API now writes to the unified deployment_states table, ensuring accurate, consistent tracking of package lifecycle states across the platform.

Generic Executor lifecycle configuration

Generic Executor artifacts now support per-phase configuration for plan, apply, and destroy. This lets you tailor behavior and scripts for each phase of the deployment lifecycle.

Dedicated service identity for scheduler jobs

Scheduler jobs now run under dedicated machine-to-machine identities (for example, [email protected]), making automated actions clearly identifiable in audit logs.

Blueprint Wizard: clickable packages and quick actions

Within the Blueprint Wizard, package names are now clickable “chips” with quick actions (view, repo, copy), plus a global “Create Blueprint” button to speed up authoring workflows.

Consistent colored tech badges on Plan page

Technology badges on the Plan page now use the same color scheme as elsewhere in the app, improving visual consistency and quick scanning.

Optimized deployment outputs API

The deployment outputs API now includes an optional metadata parameter so heavy package metadata can be skipped when not needed, improving performance on large deployments.

Stronger blueprint validation

Blueprint publishing now enforces stricter schema checks to prevent invalid or mixed artifact–blueprint configurations from being published, catching issues earlier.

Clear pre-release version visibility in package tables

Pre-release versions are visually marked in package tables, helping teams quickly distinguish between stable and experimental builds.

Environment creation moved out of the Deploy flow

The Deploy page no longer includes environment creation. Environments are created in a central location, simplifying the deployment flow and reducing accidental environment sprawl.

Blueprints on Deploy page sorted by latest version

Blueprints in the Deploy dropdown are now sorted with the newest versions first, making it faster to select the most relevant version.


🐛 Bug Fixes

Missing user data no longer blocks run history

Run history is now returned even if a user record has been deleted, ensuring historical data remains visible and auditable.

Null defaults no longer marked as required

In the Blueprint Wizard, properties with null defaults are no longer incorrectly flagged as required, aligning validation with actual configuration semantics.

Empty map overrides now supported

Empty maps {} now correctly override default values in nested map structures, giving you precise control over clearing configuration.

Complete $output autocomplete for deployments

Output variable autocomplete has been restored and enhanced with lazy loading for large datasets, so suggestions remain fast and complete even at scale.

Cost checks removed from uninstall approvals

Uninstall approvals no longer run cost validation, since uninstalls inherently reduce spend, removing an unnecessary friction point.

Fixed overlapping chips in Plan view

A visual bug where chips overlapped values in the Plan view has been fixed, ensuring each package keeps its own selected version clearly visible.

Author. Run. Observe.

This release strengthens execution visibility, improves consistency across state management, and adds powerful new authoring capabilities for YAML-based blueprints. With real-time logs, smarter state handling, and a collection of performance enhancements, this update makes deploying, debugging, and managing infrastructure smoother than ever.

🚀 New Features

Real-time log streaming for Generic Package executions

Live log streaming is now available for Generic Executor jobs, letting you watch script output as it happens. This brings the Generic Executor in line with native IaC workflows and dramatically improves debugging speed.

What it means for you: You can troubleshoot scripts in real time, catch issues earlier, and avoid waiting for long-running jobs to complete before seeing logs.


YAML blueprint support

The CLI now supports publishing slim YAML blueprints (bricks.yaml) alongside traditional bricks.json. YAML offers a cleaner, more declarative format for defining blueprint structure and metadata.

What it means for you: Blueprint authoring becomes more readable, maintainable, and version-control friendly—especially for teams standardizing on YAML.


⚡ Improvements

Unified state identifier system for deployments

A new Deployment States API introduces hierarchical Base64-encoded IDs for tracking package state. This standardizes how states are generated and stored across both legacy and new deployments.

Simplified archival to root deployments only

The archival flow now only archives root deployments—not their child deployments—reducing unnecessary work and simplifying state cleanup in large environments.

Automatic trial activation for new organizations

All new organizations now start in trial mode automatically, giving teams immediate access to the full platform experience with no manual steps.

Environment-aware package visibility

The List Packages API now respects environment-level restrictions. Non-admin users only see the blueprints and versions allowed for their environments, while admins continue to see everything.

Terraform plan reuse optimization

Terraform executions can now reuse existing plan files during the apply phase, reducing redundant plan generation and cutting runtime by 10–15 seconds per sub-deployment.

Azure resource IDs are now shortened for readability, and each one includes a direct link to the Azure Portal with a tooltip for the full ID.

Preserve temp directory on upload failure

When a blueprint publish fails, the CLI now preserves the temporary directory rather than cleaning it up—making it far easier to diagnose upload and packaging issues.

Updated Bicep badge design

The Bicep badge has been refreshed with a teal color for a consistent and recognizable visual identity across the UI.

🐛 Bug Fixes

Multi-version package publishing in Slim Bricks

Blueprints that reference the same package across multiple versions now publish correctly, resolving issues in versioned dependency handling.

Log stream completion race condition

Resolved a race condition where log streams could finish too early and lose the final buffered logs. All logs now stream through reliably to completion.

Blueprint copy/paste fixes

Copying output references (such as data. or inputs.) in the blueprint creation experience now works consistently and is correctly recognized by validation and autosuggest systems.

Blueprints, Budgets, Azure

This release delivers a big leap forward for blueprint authoring, cost control, and Azure support. A redesigned Blueprint Creation Wizard, environment cost limits, and first-class Azure/Bicep support make it easier than ever to standardize, govern, and scale your infrastructure across clouds—backed by smarter monitoring and a tighter, more reliable deploy experience.

🚀 New Features

Blueprint Creation Wizard

The blueprint builder has been completely reimagined for speed and clarity. The new Blueprint Creation Wizard lets you create, preview, and publish blueprints with real-time validation and instant Bricks.json updates, all in a single guided flow.

What it means for you: You can design complex blueprints faster and with more confidence—seeing the impact of each change immediately and reducing the risk of misconfigurations before publish.


Limit Environment Costs

You can now set monthly cost limits per environment with a dedicated cost policy. Real-time usage indicators show how close an environment is to its limit so you can keep spend under control.

What it means for you: FinOps and DevOps teams get clear, proactive cost guardrails that prevent runaway spend, making it easier to keep each environment on budget without losing deployment agility.


Azure Cloud Account Support

Bluebricks now supports connecting Azure accounts and orchestrating deployments into Azure environments, alongside existing cloud providers.

What it means for you: You can manage Azure infrastructure with the same workflows, guardrails, and visibility you use elsewhere—simplifying multi-cloud operations and expanding where you can run your workloads.


Native Azure Bicep Support

Azure Bicep is now supported end-to-end in Bluebricks. Bicep templates can be published like Terraform or CloudFormation packages, with automatic parameter and output detection, integrated state management, and full output visibility in the UI.

What it means for you: If you’re invested in Bicep, you can keep using your preferred Azure-native tooling while benefiting from Bluebricks’ orchestration, policy, and observability—making cross-cloud adoption smoother and more consistent.


⚡ Improvements

Automatic outputs for Helm artifacts

Helm artifacts now generate default outputs automatically, ensuring they’re usable from the very first deployment without extra manual wiring.

More accurate and reliable monitoring

Monitoring has been tightened to better align metrics with real-time data, remove duplicated totals, and enrich API logs with organization and resource context—making it easier to detect, debug, and resolve issues.

Clearer error banners on the Deploy page

Deploy-related errors are now consolidated into a single, prominent banner on the Deploy page so you can quickly see what went wrong and how to fix it, without juggling multiple notifications.

Enabled policies counter in Environment Policies

Each environment now shows how many policies are enabled at a glance, giving you instant visibility into the level of guardrails applied to that environment.

Polished disable-package flow in the Catalog

Action text and dialogs in the Catalog’s “Disable package” flow have been aligned and refined for a more consistent and predictable experience.

Unified Inputs section in the Blueprint Creation Wizard

The wizard now includes a dedicated Inputs section where you define global variables once and reuse them across packages, simplifying configuration and reducing duplication.

Owner approval required for force deployments

Force deployments via the Package/Install and Deployment/Create APIs now require environment owner approval, adding an extra safety check before potentially disruptive actions.

New /api/v1/packages/filters endpoint

A dedicated filters endpoint for packages improves Catalog performance by providing fast, lightweight filter data for artifacts, technologies, and tags.


🐛 Bug Fixes

Long blueprint names no longer break Deploy layout

Very long blueprint names now gracefully truncate, keeping layouts intact and ensuring buttons and controls remain accessible.

Deploy button no longer shows “undefined” while loading

The Deploy button now displays clear, intentional labels during loading states, eliminating confusing “undefined” text.

Plan drawer no longer overlaps metadata panel

On the Plan page, the right drawer can no longer be dragged over the metadata panel, preserving readability and layout clarity.

Redeploy works even when previous runs are deleted

Redeploy now functions correctly even if all prior runs have been removed, allowing you to restart deployments cleanly without getting stuck.

Fresh blueprint version when starting a new deploy

Starting a new deployment now always resets the blueprint version selection, preventing accidental reuse of a version from a previous deploy.

Blueprint selection resets correctly when changing environments

Switching environments on the Deploy page now resets related blueprint selections, keeping the deployment context accurate.

Correct value placement in Bricks.json drawer

Default and user-defined values in the Bricks.json drawer now appear in the correct fields, making configuration review more predictable.

Redeploy always preserves deployment name

Redeploy flows now consistently carry over the deployment name, avoiding missing titles in follow-up runs.

Correct blueprint version when switching deployments

When switching between deployments, the UI now reliably fetches and displays the correct blueprint version, eliminating mismatches between the deployment and its underlying blueprint.

Govern. Cost. Control.

This release strengthens environment governance and cost visibility while refining key workflows in deployment promotion, graph exploration, and package management. We’ve also improved platform resilience and cleaned up several UX issues to keep your day-to-day work smoother and more predictable.

🚀 New Features

Restrict environment blueprints

You can now control which blueprints and versions are allowed in each environment. A new Policies → Restrict environment blueprints section lets you define exactly which blueprints and versions can be deployed to a given environment.

What it means for you: You gain tighter control over what runs where—making it easier to protect critical environments, enforce standards, and prevent accidental deployments of unapproved blueprints.


Cost per package

Artifacts can now include a cost value in their metadata, which is automatically aggregated into the parent blueprint metadata for analysis.

What it means for you: Blueprints can represent not just infrastructure and configuration, but also cost. This unlocks more granular, per-component cost visibility and sets the foundation for richer cost reporting and guardrails in the future.


⚡ Improvements

Consistent task types for all tasks

All tasks now have a clearly defined task_type (install, uninstall, drift detection, and more), improving data consistency and making operational auditing easier.

Runtime-based icons for generic artifacts

Generic artifacts now automatically display icons based on their runtime (Python, Bash, Node.js, etc.), making it easier to visually scan and understand what each artifact does at a glance.

Streamlined Promote deployment flow

The deployment promotion experience has been simplified with a dedicated Promote button and modal, replacing the previous indirect flow that depended on changing the target environment.

Reduced Sentry noise from network errors

Client-side “fail to fetch” errors are no longer reported to Sentry, reducing noise in error monitoring and keeping alerts focused on issues that require action.

Clearer environment approval permission messages

When a user without the right permissions attempts to approve a deployment, the error message now explicitly explains that only environment owners can approve, providing clearer feedback.

Faster filtering on large plans

Filtering on large plans has been optimized so that working with complex deployments feels more responsive and snappy, even at scale.

Disabled “Select All” checkbox behaves correctly

When the Select All option in the Download Plan menu is disabled, its checkbox is now non-interactive as well, ensuring the UI state and behavior are fully aligned.

🐛 Bug Fixes

Accurate error messages for invalid bricks.json

Publishing a blueprint with an invalid bricks.json no longer returns a misleading “No bricks.json found” error. The CLI now surfaces precise syntax issues so you can quickly correct configuration problems.

Fixed badge spacing in Bricks.json drawer

The spacing between the “Latest” and “Technology” badges in the Bricks.json drawer has been corrected for a cleaner, more polished look.

Fixed redirect from “Have we met?” screen

Users selecting “Return home” from the “Have we met?” screen are now correctly redirected back to the login page.

Nodes now display correctly in the Graph view when filters are combined with Show Related, fixing cases where related nodes were missing from the visualization.

Long tag names now truncate correctly in Packages

Overly long tag names in the Packages view are now truncated instead of overflowing, keeping the table readable and well-aligned.

Last updated

Was this helpful?