docs: explain what query-report reports and where the query name comes from - #1253
Merged
Conversation
…s from The command's help said only that it runs a query through InfrahubGraphQLQueryReport, which names an internal type and tells a user nothing about what the answer means. Describe the consequence first: artifact and generator definitions use the verdict to decide how much to regenerate when data changes. State the rule that produces it, note that NAME comes from the queries section of .infrahub.yml, and record on --branch that the answer is branch-dependent because uniqueness constraints live in the schema.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## stable #1253 +/- ##
==========================================
+ Coverage 82.47% 82.54% +0.06%
==========================================
Files 138 138
Lines 12186 12186
Branches 1833 1833
==========================================
+ Hits 10051 10059 +8
+ Misses 1572 1568 -4
+ Partials 563 559 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes 🚀 New features to boost your workflow:
|
gmazoyer
approved these changes
Aug 19, 2026
gmazoyer
left a comment
Contributor
There was a problem hiding this comment.
Does this actually need a changelog?
Contributor
Author
No I guess that's a bit redundant for this. |
Deploying infrahub-sdk-python with
|
| Latest commit: |
8deae32
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3764716a.infrahub-sdk-python.pages.dev |
| Branch Preview URL: | https://pog-query-report-help-text.infrahub-sdk-python.pages.dev |
ajtmccarty
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Improves the help text for
infrahubctl graphql query-report. No behavior change.The command's description was "Run a GraphQL query through InfrahubGraphQLQueryReport and report its analysis." That names an internal server type and tells a user nothing about what the answer means or why they would want it.
It now:
truemeans only the objects that changed are reprocessed,falsemeans all of them are.NAMEthat it is the query name declared underqueriesin.infrahub.yml.--branchthat the answer is branch-dependent, because uniqueness constraints come from the schema.Kept as plain prose with no markdown links, since the same text renders in terminal
--help.Rendered output
Regenerated with
uv run invoke docs-generate;docs/docs/infrahubctl/infrahubctl-graphql.mdxis included.Related
The Infrahub docs are updated in a companion PR (opsmill/infrahub#10293), which documents the command on the canonical Single-target queries page. The concept this command reports on is called a single-target query in user documentation.
Testing
uv run invoke formatanduv run invoke lint-code- cleanuv run invoke lint-docs- no findings on the changed pages (20 pre-existing spelling errors remain in generatedsdk_ref/files)Summary by cubic
Clarifies the help text for
infrahubctl graphql query-reportso users understand the verdict, the uniqueness rule, where the query name comes from, and branch dependence. No behavior change; this clarifies how artifact and generator definitions determine regeneration scope.infrahub_sdk/ctl/graphql.pyand the docs pagedocs/docs/infrahubctl/infrahubctl-graphql.mdx.NAMEis from thequeriessection of.infrahub.ymland that--branchcan change results because constraints come from the schema.Written for commit 8deae32. Summary will update on new commits.