Infrahub 1.7 makes Infrahub easier to run as a dependable system of record for infrastructure data in environments where governance, accountability, and operational clarity matter.
The focus is practical: better auditability on every object, stronger reuse patterns through Profiles, and a smoother day-to-day experience when you’re inspecting objects and managing change workflows.
We’ve also upgraded core backend dependencies to keep the platform current and maintainable.
Audit metadata (who/when) available on every object
In 1.7, every object now carries read-only metadata about when it was created and last updated, and who made those changes.
This information is a foundational piece for teams that need stronger data governance around infrastructure intent. Now, reviews are easier, accountability is built-in instead of process-driven, and it’s much simpler to answer basic questions during debugging or post-incident follow-ups.
This metadata is available through the UI, GraphQL API, and Python SDK, so it’s usable both by humans reviewing changes and by tooling that needs to reason about data history, such as for reporting, queries, or internal audit workflows.
Profiles can now include relationships
Profiles in Infrahub are a way to define reusable patterns, including attribute values and relationships, that can be applied consistently across many objects instead of configuring each object individually. Think of profiles as object data blueprints that allow you to easily keep data consistent.
For example, let’s say you want to define a standard set of RADIUS servers that network devices in a specific region will use. In Infrahub, you can define profiles for device objects in each region. Each profile would define the RADIUS servers to be used in that region. Every device in that region will use the region-specific device profile and inherit the RADIUS servers defined in it.
This makes it easy to guarantee that all the devices in a specific region use the same RADIUS servers. But you also have the flexibility to use one-off configurations by overriding the RADIUS servers at the device object level.
Profiles remember the objects they’re applied to. This means you can make modifications to a profile, and those changes will automatically propagate to the objects the profile is applied to. This allows you to easily update standards or blueprints over time.
For example, in the above scenario we could easily update the particular RADIUS servers that should be used in a region just by updating the profile.
Other scenarios where profiles are helpful:
- Predefining interface configurations (MTU/VLANs/Layer 2 mode/...) for access ports, server ports, or infrastructure ports
- Migrating scattered brownfield configurations to standard compliant configurations
Redesigned object detail view for faster context and actions
A lot of day-to-day work in Infrahub happens in the object detail view—understanding what an object is, how it’s modeled, which Profiles influence it, and what Groups it belongs to—then taking action. In 1.7, the object detail page has been redesigned to make that context easier to access without bouncing across multiple screens.
The intent here is straightforward. When you’re reviewing data, troubleshooting, or validating automation inputs, you should be able to quickly answer, “What is this object, how is it shaped, and what’s applied to it?” and then take action (such as managing Groups and Profiles, or jumping to the schema) without having to switch between a bunch of screens.
Better branch list experience in large environments
Some teams keep a large number of branches active in Infrahub to support parallel work and review workflows. In 1.7, the branch list page has been updated to work better at that scale, including pagination and partial-name search.
This sounds like a small change but has a big impact in practice. When branch counts grow, finding the branch you need—quickly and reliably—becomes part of keeping change workflows moving. The updates here are aimed at making the task of finding the right work faster and less frustrating.
A stronger, modernized foundation under the hood
Infrahub 1.7 upgrades core backend dependencies for Python, Neo4j, RabbitMQ, Redis, and PostgreSQL.
This is important for teams running Infrahub as part of their automation stack. It keeps dependencies current, supports long-term maintainability, improves security posture through updated patches, and creates a healthier base for future development.
Get Infrahub 1.7
For teams using Infrahub as a shared source of infrastructure intent, these changes make that work more reliable and easier to manage.
Get the full release notes, including implementation specifics, on GitHub.