Infrahub 1.8 expands what infrastructure teams can treat as part of their source of truth while strengthening how infrastructure changes move through their lifecycle.
This release introduces file objects as first-class data, automatic resource allocation from templates, and stronger branch lifecycle controls, alongside preserved change diffs, simplified Git repo updates, and Kubernetes-ready backup support.
Together, these make Infrahub a more complete and reliable platform for infrastructure automation.
Bringing supporting files into the source of truth
Infrastructure teams rarely work with structured data alone. Contracts, service orders, diagrams, configuration backups, and compliance reports often contain critical context.
Traditionally, these files and documents live outside the source of truth in document repositories or ticketing systems. This separation introduces friction: You have to switch between systems, permissions may not align, and documents can easily drift out of sync with the infrastructure they describe.
Infrahub 1.8 introduces file objects as first-class data, allowing you to store and relate files directly within the infrastructure graph, accessed through the same APIs, permissions, and relationships that govern other data in Infrahub.
For example, you can now:
- Attach telecom contracts directly to circuits or services
- Store configuration backups alongside the devices they describe
- Link compliance reports to the infrastructure components they evaluate
By bringing both structured infrastructure data and supporting files into the same system, Infrahub helps you maintain a more complete record of your environment.
Resource allocation, automatically
Templates are how you create devices, services, and objects consistently at scale.
Previously, templates referencing resource pools sometimes required additional steps to allocate resources, such as IP addresses, IP prefixes, or number pool resources, after the object was created.
Infrahub 1.8 simplifies this by allocating resources at the moment an object is created from a template.
Templates now store the pool reference, and the allocation occurs automatically during object creation. This eliminates a common source of operational friction and reduces the likelihood of late failures in CI pipelines or automation workflows.
If you're building service catalogs or automated provisioning systems, this means templates behave more predictably. Creating an object from a template now produces a fully allocated and automation-ready object from the start.
Reliable audit trails even after branch cleanup
Infrastructure teams frequently delete branches once changes are merged to keep environments clean. But the history associated with those changes remains important for audits and incident investigations.
Infrahub 1.8 ensures that Proposed Change diffs remain available even after a branch is deleted.
Diff data is now tied directly to the Proposed Change itself rather than the branch lifecycle. Even if a branch is removed as part of normal cleanup, the full history of the change remains accessible.
Simplifying Git repository updates
Many teams import read-only external Git repositories into Infrahub for schema definitions, documentation, or automation logic. Keeping these read-only repositories up to date previously required manually copying commit hashes from external tools.
Infrahub 1.8 introduces an Update to Latest action in the UI that fetches the most recent commit for the tracked branch directly, without needing to copy commit hashes manually. Repositories can also track Git tags for clearer versioning and reproducibility.
Production-ready backup for Kubernetes deployments
As more organizations deploy Infrahub in Kubernetes environments, consistent backup and restore workflows are essential.
The infrahub-backup CLI now includes full Kubernetes support. You can now schedule backup and restore operations using Kubernetes Jobs or CronJobs through the Helm chart.
The backup and restore workflow handles service coordination, database dumps, and metadata generation while supporting S3-compatible storage backends.
For teams operating Infrahub in production clusters, this provides a predictable and Kubernetes-native approach to protecting the infrastructure data that powers their automation.
Additional improvements
Infrahub 1.8 also includes a range of smaller improvements that enhance everyday usability.
User interface
- Improved visibility within Proposed Change views. Tab counts now appear across all tabs (Data, Files, Artifacts, Schema, Checks, Tasks), and diff badges indicate whether items were added, removed, or updated.
- Expanded branch list details. Details now show who created each branch, links to associated proposed changes, rebase status, schema change indicators, and a merged badge. Merged branches are also filtered out of the Proposed Change creation form.
- General UI improvements. Clicking an attribute or relationship label opens the schema viewer at that field definition. Field-type icons indicate attribute types at a glance. A refresh button with last-updated tooltip has been added to task views. Focus outlines are now consistent across all interactive elements.
Reliability, performance, and developer experience
- Frozen branches after merge. Branches are automatically locked once merged, preventing them from being modified or re-merged. This makes it clear which branches are no longer needed, laying the groundwork for automatic branch deletion in 1.9.
- More reliable schema updates and data migrations. Schema updates and data migrations are now handled as a single atomic operation, preventing incompatible states if a migration fails mid-way.
- Improvements to validation, error reporting, and SDK behavior. The SDK now correctly handles cascade deletions in generator workflows, list attributes support regex validation, and data tables show clear error messages when API requests fail.
Why this release matters
Infrahub is designed to be the authoritative data layer for infrastructure automation, where infrastructure models, operational data, automation logic, and change workflows all live together.
With Infrahub 1.8, we're moving further in that direction. You can now store supporting files alongside infrastructure objects, allocate resources automatically when provisioning from templates, and rely on stronger change lifecycle guarantees.
The result is a more complete source of truth that teams can confidently use to drive automation at scale.
