Summary and goal

Move the backend functionality out of the Chrome service into a stand-alone service. The backend will soon be required by other services in HCC. There are also talks about non-HCC applications interested in the widget dashboard. The frontend requirements are discussed with PF; however, the backend should be decoupled from the Chrome service to enable non-HCC app integrations.

Acceptance Criteria 

1. Extract the widget layout code to a new service
2. Implement widget configuration collection via FEO
   1. use a separate config map from chrome UI configuration to prevent exceeding the size limit and ensure logical separation of data 
3. Inject FEO generated widget configuration into the widget layout pod(s)
4. AppInterface onboarding (can be done in paraller)
5. An SOP is created/updated to ensure this deployment process is repeatable and can be done again solely by following the SOP. The SOP should be written down during stage env migration and executed for prod env migration. The SOP should be stored in app-interface under https://gitlab.cee.redhat.com/service/app-interface/-/tree/master/docs/tenant-services/console.redhat.com/app-sops

Checklist

Open Questions