ui: remove ui-configuration.graphqls — template CRUD moves to REST#162
Merged
Conversation
apache/skywalking 11.0.0 introduces a `ui-management` feature module that mounts on the admin-server REST host and serves dashboard template CRUD over HTTP at `/ui-management/templates/*` (UIManagementRestHandler). The GraphQL UIConfigurationManagement resolver is removed in the same release, leaving every type declared in this file (DashboardConfiguration, NewDashboardSetting, DashboardSetting, TemplateChangeStatus, getTemplate, getAllTemplates, addTemplate, changeTemplate, disableTemplate) without a resolver. Delete the file rather than ship schema entries that no backend honors.
wu-sheng
added a commit
to apache/skywalking
that referenced
this pull request
May 19, 2026
* docs/en/FAQ/v9-version-upgrade.md: drop the ui-configuration.graphqls URL that 404s now that the schema was removed upstream in apache/skywalking-query-protocol#162; rewrite the bullet to reference the file historically without an external link. * test/e2e-v2/cases/cilium/e2e.yaml: namespace regression — when I re-pointed the kind expose-ports from skywalking-ui:80 to skywalking-oap:12800 I also accidentally flipped the namespace from kube-system (where this stack actually installs skywalking) to istio-system, so the e2e timed out on 'namespaces "istio-system" not found'. Restore kube-system.
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.
Summary
apache/skywalking 11.0.0 introduces a `ui-management` feature module
that mounts on the admin-server REST host and serves dashboard template
CRUD over HTTP at `/ui-management/templates/*` (UIManagementRestHandler:
GET list, GET by id, POST add, PUT change, POST disable).
The GraphQL `UIConfigurationManagement` resolver is removed in the
same release, leaving every type declared in this schema file —
`DashboardConfiguration`, `NewDashboardSetting`, `DashboardSetting`,
`TemplateChangeStatus`, plus the `getTemplate` / `getAllTemplates`
queries and `addTemplate` / `changeTemplate` / `disableTemplate`
mutations — without a backend resolver. Delete the file rather than
ship schema entries that no backend honors.
Operator migration: switch from `getAllTemplates` /
`addTemplate` etc. to the equivalent REST calls on the admin host
(default :17128). Documented at apache/skywalking/docs/en/setup/backend/admin-api/ui-management.md.
Test plan
(11.0.0: drop bundled UI, retire status public REST, add ui-management + queryAlarms skywalking#13877 confirms — no resolver references it).
🤖 Generated with Claude Code