openmcp-project / openmcp-project/backlog
Ship Webapp as a `PlatformService`
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
As a team operating Open Control Plane stack in my organization.
I want to give all teams simple access to the https://github.com/openmcp-project/ui-frontend that belongs to this project.
Depends on
- https://github.com/openmcp-project/backlog/issues/514
- Make UI-Frontend truely whitelabel
- Branding (org internal name may differ, logos of org hosting this)
- Custom OTEL endpoints
- ....
Scope
PlatformServiceis available for Operators to install- End users of platform can consume Projects/Worksapces/ControlPlanes and their content via UI
- Solution is customizable (B)
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 dependency on backlog issue 514 and the openmcp-project/ui-frontend project, then clarify how the webapp should be packaged as an installable PlatformService. Define the required whitelabel branding and custom OTEL endpoint behavior before implementation. Done means Operators can install it and platform users can access Projects, Workspaces, ControlPlanes, and their content through the customizable UI.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100