What problem does it solve? Writing Infrahub checks requires coordinating three components — a GraphQL query, a Python InfrahubCheck class, and .infrahub.yml registration — and common mistakes like adding a forbidden query field or calling a nonexistent log_warning method cause silent passes or config validation failures. ## Core Features & Use Cases - Check Authoring Guidance: Walks through building global and targeted checks, from GraphQL query design to validate() implementation with correct log_error/log_info usage. - Registration Rules: Documents the exact .infrahub.yml check_definitions shape, including the extra="forbid" constraint that rejects a query field and the targets/parameters mapping for targeted checks. - YAML-Driven Testing: Covers the Resources Testing Framework with check-smoke, check-unit-process, and check-integration test kinds plus fixture directory structures. - Use Case: You need to block proposed changes when two devices occupy the same rack unit. The skill guides you to write a rack_devices.gql query, a RackUnitCollisionCheck class, register it in .infrahub.yml, and add pass/fail unit tests with JSON fixtures. ## Quick Start Create an Infrahub check that validates no two devices share the same rack unit position and register it in .infrahub.yml.
