We should determine how – and if – plugins will be able to use the Redux store.

Use Case: Migrating legacy applications that use Redux to plugins. For instance, OCM uses Redux heavily, and we plan to migrate OCM pages into HAC. If we can keep using Redux, it avoids a lot of rework of the OCM code. OCM does not need to read anything HAC core sets in Redux. It simply wants to read and write its own data to the store.

Today, OpenShift console has a Redux reducer extension point (core.redux-reducer) where plugins can contribute reducers and then use the useSelector hook to get the data later.

• Do we allow plugins to use Redux, or do we ask them to use React context instead?
• Do we keep the same core.redux-reducer extension from OpenShift console?
• Is there a way to separate/protect HAC core's Redux data from plugins?

Related to HAC-395.

cc kdoberst christianvogt psavage@redhat.com aballantyne