openmcp-project / openmcp-project/backlog
Epic: Switch to crd-gql-gateway as UI backend
Open
Nobody has claimed this yet.
area/webapp
kind/epic
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Understand the Epic
Calls to the old REST ui backend should be replaced with calls to the new crd-gql-gateway.
Context / Background
After a spike, we decided to switch to the new backend.
User Stories or tasks
What is required to accept the Epic as finished.
- Communication with Onboarding API happens via GraphQL
- Old backend is removed from UI
- Follow-Up: Solution for caching inside the gateway (needed?)
Dependencies of this Epic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the old ui-backend, the crd-gql-gateway, and the linked gateway proposal for MCP support. Trace how the UI communicates with the Onboarding API and identify the affected calls. The epic is done when that communication uses GraphQL, the old backend is removed from the UI, and the caching question has a documented solution or decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100