As network and infrastructure automation becomes more central to daily operations, teams need to manage more than device inventory. Infrastructure data, automation definitions, configuration generation, and validation all need to evolve together, with the reliability and control required for production environments.
With Infrahub, engineers can model their infrastructure, review changes to data and automation together, and generate configurations from validated infrastructure data.
Infrahub 1.12 strengthens these workflows with more reliable Git integration, resource allocation that accommodates existing infrastructure, and performance improvements for large infrastructure changes.
The release also makes it easier to review infrastructure information, test automation changes against individual devices or services, and use infrastructure context in external systems. And dark mode is now available in alpha.
More reliable change management across Infrahub and Git
When engineers change infrastructure data and the automation that consumes it, they need to review and validate both before applying the changes to production.
With Infrahub, teams can maintain YAML schema definitions, Generator and Transformation code, and configuration templates in Git. Infrahub imports these definitions so engineers can test them alongside infrastructure data on an Infrahub branch. Proposed Changes provide a way to run validation checks, review the results, and approve changes before merging them into the default branch.
In 1.12, teams can manage infrastructure changes more reliably by verifying that the required Git-managed definitions have been imported successfully before merging. If an import fails, engineers can investigate the problem while continuing to develop and test changes on other branches.
The release includes several improvements:
- Verify changes before merging: Review repository import status and confirm that the intended Git commits have been imported successfully. If a required import fails or remains incomplete, Infrahub prevents the branch from being merged into the default branch.
- Recover when a remote Git repository can’t be updated: If an Infrahub branch merge completes but the corresponding push to the remote Git repository fails, you can inspect the error and retry or abandon the pending push.
- Continue testing changes on other branches: An import failure affecting one Git branch no longer prevents imports on other branches, allowing engineers to continue validating changes while resolving the error.
- Review updates before importing them: For read-only repositories, you can inspect newly detected Git commits and choose when to import them into Infrahub.
These capabilities are particularly valuable for teams managing infrastructure automation across multiple Git branches, repositories, and CI pipelines.
By managing infrastructure data alongside the automation that consumes it, engineers can review and validate both as part of the same proposed infrastructure change.
Automate existing networks with more flexible resource allocation
Network automation rarely starts with an empty network.
Most teams already have VLAN IDs, ASNs, and other resources assigned across their infrastructure, often using different numbering conventions between sites, regions, or network domains.
With Infrahub 1.12, teams can extend automated resource allocation across their existing networks, preserving established VLAN and ASN assignments while consistently provisioning new devices and services across sites.
Infrahub Resource Manager now supports:
- Managing existing and new assignments together: Associate VLAN IDs and ASNs already in use with a number pool, so future allocations account for those assignments.
- Allocating across multiple ranges: Combine ranges such as VLAN IDs 100–199 and 300–399 within a single pool, with control over their allocation order.
- Manage independent allocations through one pool. Allocation scopes maintain a separate number sequence for each scope without requiring engineers to create and maintain a separate pool for each one. For example, the same VLAN ID can be assigned at different sites while remaining unique within each site.
- Understanding available capacity: Review utilization by range or site and identify which objects hold existing assignments.
For example, an organization with dozens of sites can manage VLAN assignments through one number pool while maintaining the numbering conventions already used at each location.
Teams can progressively bring existing assignments into Infrahub without renumbering their network and use the same resource allocation capabilities when provisioning new devices and services. Existing assignments must be associated with a pool to be included in allocation tracking.
Because the Resource Manager works with Infrahub’s user-defined schema, engineers can incorporate resource allocation into their infrastructure and service models rather than tracking assignments separately from the devices and services that use them.
Keep automation responsive as infrastructure grows
As teams model more devices, services, and relationships in Infrahub, a single infrastructure change may affect hundreds or thousands of objects.
Infrahub 1.11 introduced more selective regeneration and recomputation, reducing processing for definitions and objects that weren’t affected by a change.
Version 1.12 builds on those improvements to help teams maintain efficient change and validation workflows as the number of devices, services, and automation tasks grows. Engineers can validate large infrastructure changes sooner, while teams responsible for operating Infrahub gain better visibility into the causes of slow automation and API requests.
The release includes several improvements:
- Faster computed attribute recalculation: After a branch merge or rebase, Infrahub now recalculates Python computed attributes in batches, reducing the number of background tasks required before dependent Generators and artifacts can use updated values.
- More efficient Proposed Change validation: Artifact and user checks make fewer repeated API requests when validating large groups of objects, reducing API server load and the time needed to complete validation.
- Better performance diagnostics: Expanded OpenTelemetry tracing and metrics help engineers identify expensive database queries and distinguish execution time from delays caused by task queues or database connection availability.
- Investigate issues without restarting Infrahub: Administrators can temporarily increase trace sampling to collect additional information while investigating intermittent performance problems.
Together, these improvements help engineers validate large infrastructure changes more efficiently and give teams operating Infrahub the diagnostic information they need to investigate performance problems.
Improvements across the platform
Additionally, 1.12 includes improvements to how you find and review infrastructure information, test automation changes against individual devices or services, and provide meaningful infrastructure context to other systems.
Customize your views and work in dark mode
Dark mode is now available in alpha! You can choose a dark appearance, switch to light mode, or have Infrahub automatically follow your operating system’s theme.
You can also customize which attributes appear in object lists, relationship tabs, and IPAM tables. Share your column selections through the list URL so colleagues can review the same information.
Other UI improvements include smoother scrolling through large Proposed Change diffs and pan-and-zoom support for SVG artifacts, making detailed network diagrams easier to inspect.
Test and regenerate individual objects
When developing or troubleshooting a Generator, you can now run it for a specific target object rather than the entire group. For example, you can test changes to a Generator against a single device before running it across all its targets.
When you update an artifact or Generator definition in .infrahub.yml, Infrahub also avoids regenerating other definitions whose configuration hasn’t changed, subject to their configured file-change dependencies.
Build integrations with more useful infrastructure data
When integrating Infrahub with ticketing systems, chat notifications, or audit records, you can now use the human-friendly IDs and display labels included in webhook events to identify affected infrastructure objects without additional API queries.
For engineers developing scripts and integrations with Infrahub’s Python SDK, you can retrieve only the attributes and relationships needed for a particular operation, handle API failures using structured error codes, and trace requests into the Infrahub API server when investigating performance issues.
Manage access and permissions more reliably
When managing API tokens, Infrahub now verifies token ownership before allowing deletion.
Changes to global permissions made on an Infrahub branch also remain isolated until the branch is merged into the default branch, so engineers and administrators can review permission changes before they affect user access.
Sensitive identity information is now masked before diagnostic traces are exported.
Get Infrahub 1.12
Infrahub 1.12 strengthens the data, automation, and change management capabilities that teams rely on in production. From reviewing Git-managed changes to allocating resources across existing networks, this release helps teams extend network and infrastructure automation while maintaining control over how infrastructure changes.
For the complete list of changes, including breaking changes and upgrade instructions, see the Infrahub 1.12 release notes.
