Epic: ApeioRA Showroom UI Support #322
Description
Understand the Epic
We need to make our UI customizable to be integrated into the ApeiroRA Showroom UI.
This requires some more configuration options (preferable through a Kubernetes Resources based API) to disable some of our UI features.
The Onboarding UI is not needed in ApeiroRA as we will link directly to an MCP.
The UI will be implemented as an iFrame with the direct link to an MCP. It should also use the auth token provided via a parameter (e.g. query parameter).
Context / Background
This epic contains everything about making our UI ready for the ApeioRA Showroom.
The UI will be implemented using an iFrame and should link to the MCP view directly, as every Account in the Showroom will only get one MCP.
As there is already a UI from the Showroom itself (provided by the Platform Mesh) we will only be integrated in the part for the MCP of an Account. This is why we dont need our Onboarding API UI part (project, workspaces, MCP CRUD) and just the part where the detail page of the MCP is shown.
User Stories or tasks
I as a user of the ApeiroRA showroom want to see the details of my MCP linked to my apeiroRA Account.,
I as a platform operator of the ApeiroRA showroom want to enable the MCP UI for my end users.
I as a platform operator of the ApeiroRA showroom want to configure the MCP UI using a Kubernetes Resource (on the platform cluster) for my users.
What is required to accept the Epic as finished.
- UI is installable in a configured way so it only supports direct MCP links and shows only the detail view of an MCP
- UI is configurable to get the auth token of a user via a parameter when embedded via an iFrame
Dependencies of this Epic
No response
Risks of this Epic
No response
Known Stakeholders of this Epic
- ApeiroRA End Users (User using the ApeiroRA Platform Mesh platform)
- ApeiroRA Platform Mesh Operators
Milestone Definitions for this Epic.
No response
Metrics Definition for this Epic.
No response
Any further valuable resources.
No response