Repository navigation
Add ExportAccessControlCounts to StartExportFlow in generated schema - #173
Merged
Merged
Conversation
rmennes
enabled auto-merge
November 9, 2026 14:43
|
TimmersThomas
approved these changes
Nov 9, 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.





📝 Description of the changes
Adds access control counts (grants, groups, shares, masks, filters) to the export flow's
StartExportFlowresponse, so clients can see how many access control entries an export carries when it starts. The GraphQL query, its generated Go types, and the publictypesaliases are updated together to keep the client in sync with the schema.Export Flow API
StartExportFlowfragment to requestaccessControlCounts, reusing a newExportAccessControlCountsfragment (internal/schema/queries/exporter.graphql).ExportAccessControlCountsstruct with getters for each count field, and wired it intoStartExportFlowandTriggerExportFlowStartExportFlow(internal/schema/generated.go).TriggerExportFlowquery string to include the new selection and fragment (internal/schema/generated.go).Generated Types
ExportAccessControlCountsandStartExportFlowAccessControlCountsExportAccessControlCountsas type aliases in the publictypespackage (types/generated.go).Impact & Risk
TriggerExportFlowresponse now includes an additionalaccessControlCountsobject. Clients that decode strictly or compare full payloads may need to account for it.types/generated.gowere not reviewed.🎫 JIRA reference
No JIRA ticket detected.