Skip to main content

Release 1.2.7

Release Number1.2.7
Release TypeImprovement
Release DateJune 16th, 2026
Tagv1.2.7

Release summary​

When you build a generator that works through the results of a query, you can now read each related object from the response it already returned instead of sending a separate request for each one. For generators that handle many objects, that means far fewer requests.

Build generators that reuse query results instead of requesting each object​

Build a generator with the managing-generators skill so that, when its query already returns the related objects it needs, the generated code builds them from that response instead of fetching each one again.

  • Create related objects from the data already in the query response with from_graphql, instead of calling client.get once per object.
  • Follow the query-coverage requirement so the response carries everything those objects need: __typename, id, and every attribute the generator changes.
  • Use the before/after example in managing-generators to refactor an existing generator.

Full changelog​

Added​

  • from_graphql rule for managing-generators: build related objects from the query response instead of requesting them again (#58).

Skills included​

  • infrahub-managing-schemas
  • infrahub-managing-objects
  • infrahub-managing-checks
  • infrahub-managing-generators
  • infrahub-managing-transforms
  • infrahub-managing-menus
  • infrahub-auditing-repo
  • infrahub-analyzing-data
  • infrahub-reporting-issues
  • infrahub-collecting-diagnostics