-
Spike
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
We should start with using of the getK8sResourceURL from Core SDK, instead of console's getK8sResourcePath that we export and use from the Console SDK.
At first we should determine if its even feasible for console to outsource its utils package to OpenShift Dynamic Plugin SDK, since:
- its not in sync with console logic
- is out of date
- wont slow down the development of console
Acceptance Criteria
- Import form Core SDK & Export from OpenShift Console SDK
- Find one use case of each import and make sure the new import from the Core SDK works
- Deprecate the old Console SDK instance of this one
- Log a tech debt story to follow up the other instances
- clones
-
CONSOLE-3216 Refactor OpenShift Console to use k8s-utils from the Core SDK
- To Do
- is cloned by
-
CONSOLE-4320 Determine feasibility of using dynamic-plugin SDK utils pkg
- To Do
- is depended on by
-
CONSOLE-3216 Refactor OpenShift Console to use k8s-utils from the Core SDK
- To Do