24 07 2026 schema dump#629
Open
andrewstillv15 wants to merge 4 commits into
Open
Conversation
The backend's public schema now exposes OnCall, OnCallConnection, and KubernetesIntegrationInput, which client-gen correctly generates for real for the first time. Remove the now-duplicate hand-rolled definitions in on_call.go/integration.go, and update service.go's GetOnCalls to match the generated OnCallConnection's Nodes-only shape (no Edges field, consistent with every other Connection type). Also switch ConnectServiceRepository's BaseDirectory to the plain *string helper: the backend has always validated allow_null: false on ServiceRepositoryCreateInput.baseDirectory, and the freshly-extracted Tier 1 nullability facts now generate it correctly as *string instead of the historical *Nullable[string] default. Add ApiTokenOwner as a hand-maintained union type in union.go, following the same inline-fragment pattern as the other unions here (e.g. ServiceDocumentSource) -- the backend added a new ApiToken type with a tokenOwner: ApiTokenOwner union field that client-gen has no way to generate on its own.
…ction Unused-so-far Connection types picked up now that a real client-gen regen runs against the current schema: CampaignTeamConnection from unblocking Campaign generation, OnCallConnection now that the backend publicly exposes OnCall, and PackageConnection for the new Package type. Verified against the backend GraphQL type definitions.
…ategory Picks up new enum values validated against backend source: Package* enums for the new Package type, EventIntegrationEnum's snykEvent/ sonarqubeEvent (deprecation replacements), HasDocumentationSubtypeEnum openapi, PayloadFilterEnum integration_id, RelationshipDisplayStatusEnum hidden/visible, SecretAccessControlEnum everyone/owner_only, and ServiceFilterEnum maturity_enabled. Also includes backend doc-string wording fixes picked up along with the regen. PredicateKeyEnum.component_category is preserved via the new client-gen special case (see the opslevel-client-gen submodule bump) since it's still a documented Terraform provider filter key despite the backend marking it non-public.
Pure description-text fixes picked up from the backend's GraphQL schema docs (typos, capitalization of ID/URL/SHA/YAML/HTTP, minor grammar) -- no field or type changes.
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
1 participant
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.
Problem
The generated public schema is wayyy behind, making the generated diff unmanageable. This MR brings the generated types inline with the current public schema.
Solution
Checklist