Infrahub v1.8.0b0 - Release Notes

⚠️ !!! WARNING This first beta version of Infrahub v1.8.0 is supposed to be used for testing purposes only.

We're excited to announce the first beta release of Infrahub v1.8.0! This release focuses on strengthening Git integration workflows, improving operational tooling, and expanding template capabilities.

Version 1.8 introduces file attachments on objects, enables resource pool references in templates, and delivers key Git workflow improvements including the ability to view proposed change diffs after branch deletion and automatic branch freezing after merge. We've also added full Kubernetes-native backup support and several usability improvements across the platform.

Main changes

File attachments

Infrahub now supports attaching files directly to objects, enabling users to store and reference documents such as contracts, configuration files, or diagrams alongside their infrastructure data.

Files are managed through the UI and API, providing a centralized location for documentation that is directly associated with the relevant infrastructure objects.

Resource pool references in object templates

Object templates can now reference resource pools, enabling automatic resource allocation when creating objects from templates.

Previously, templates could define static attribute values and relationships, but any resource allocation (IP addresses, ASNs, VLANs, etc.) had to be done manually after object creation. Now you can:

• Reference resource pools directly within a template definition
• Automatically allocate resources when creating objects from templates
• Enforce consistent, policy-driven allocations across teams and environments
• Reduce manual steps and eliminate late-stage CI/generator failures caused by missing allocations

This reduces operational overhead, minimizes human error, and makes common provisioning workflows work end-to-end from a single template.

View proposed change diff after branch deletion

Users can now consult the diff and changes of a proposed change even after the source branch has been deleted from Infrahub.

Previously, deleting a branch would make it impossible to review the changes that were part of that proposed change.

This capability is also a prerequisite for automatic branch cleanup after merge.

Freeze branch after merge

Branches are now automatically frozen after being merged via a proposed change, preventing accidental modifications to already-merged branches. This ensures the integrity of your change management workflow and eliminates a class of errors where users would inadvertently push changes to a branch that had already been merged.

Full changelog

Added

• Added the ability to also fetch tags from git (#8078)
• Added Builtin to the list of restricted namespaces
• Added CoreFileObject generic for storing files as node attributes with branch-aware versioning. Nodes inheriting from CoreFileObject support file upload via GraphQL mutations and download via REST API endpoints.
• Added a refresh button to the task list and details view with a tooltip showing the last data refresh time
• Added a shortcut in the object details view: clicking an attribute or relationship label opens the schema viewer modal, directly showing and scrolling to the relevant field definition
• Added ability to view artifact changes from the branch details view
• Added consistent focus outline color across all interactive elements for improved visual accessibility
• Added counts to proposed change tabs
• Added icons next to field names in the object details view to indicate field types (e.g., text, number, boolean) and relationship schemas
• Added status badges to file and artifact diffs showing the type of change (added, removed, updated)
• Added tooltip over action buttons (download/copy) on artifact details view.

Changed

• Improved consistency of GraphQL Query details page with other object views
• Remove "Task Overview" title from embedded task tabs (object that inherit from CoreTaskTarget)
• Simplified default branch view by hiding inapplicable actions and tabs
• Use Jinja2 templates to compute display labels of permission objects, also mark identifier as deprecated

Fixed

• Handle schema updates and associated data migrations as a single item so that an unexpected failure during a schema migration does not leave the schema and data in incompatible states. This applies to loading a schema, merging a branch, and rebasing a branch. (#6948)
• Allow List attributes to use the regex parameter for validating list item values (#7717)
• Shift-click range selection now anchors to the last clicked row, with added e2e coverage for range toggling. (#8229)
• Fixed error reporting on invalid Jinja2 templates for display_labels (#8311)
• Add full support for updating existing Template instances via schema migrations when the associated node or generic schema is updated in a manner that would add or remove attributes to or from the Template's schema.
• Allow generating Template schemas for both a generic schema and a node inheriting from that generic. Previously, schema validation would raise a validation error and prevent this.
• Data tables now display error messages when API requests fail due to permission or other errors.
• Fix task view showing "Name not found" for related nodes that exist only on a branch by querying the correct branch and time context.
• Fixed adding a relationship from a resource pool within relationship tabs in the object detail view
• Fixed an issue where Infrahub was calculating the wrong authentication signature caused by HTTPX v0.28.0 switching to compact JSON payload encoding.
• Fixed issue where system user showed as the last user changing a proposed change after merge