-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
5
-
False
-
-
False
-
-
-
5
-
OCMUI Core Sprint 256, OCMUI Core Sprint 257, OCMUI Core Sprint 258, OCMUI Core Sprint 259, OCMUI Core Sprint 260, OCMUI Core Sprint 261, OCMUI Core Sprint 262, OCMUI Core Sprint 263, OCMUI Center Team Sprint 273, OCMUI Center Team Sprint 274, OCMUI Center Team Sprint 275
We should take another look at our config/build and try to standardize with how frontend apps are configured nowadays. So far, this is not required, but a ‘nice to do’ to be inline with other HCC tenant setups. At some point it might become necessary for an urgent fix/change. For example, this ticket was initiated by an "Actions Required" urgent announcement for HCC about "local development change". In this case, OCM UI didn't have to do anything.
- ‘Should’ work with our local dev build / server
Bryan put together a PoC showing how to switch to FEC in this branch
https://github.com/florkbr/uhc-portal/commits/hcc-fec-build-tool-poc/
More info and links can be found in the slides Bryan put together recently (Slides 14-21):
The FEC binary also provide a command to setup the initial hosts configuration to run the app locally. We should remove our own script and provide instructions on how to use the FEC one in our README.
In general we should double check all the features provided by fec and verify if there is anything in our repo that can be replaced by them.
Acceptance Criteria
- Create a fec config file, replaces webpack config.
- Weekly promotion unaffected
- is depended on by
-
OCMUI-3698 Ensure that OCM-UI remains functional after the FEC stage deployment.
-
- Closed
-
-
OCMUI-3330 [HCC Action required] Frontend Operator (FEO) Migration
-
- Closed
-