This story describes Phase 2 of using OpenShift Dynamic Plugin SDK in Console.

This story is focused on plugin runtime infrastructure.

Console code should be updated as follows:

• add dependency on @openshift/dynamic-plugin-sdk
• replace Console PluginStore with one from OpenShift Dynamic Plugin SDK
• ensure PluginStore instance interops with Console feature flags
• replace Console TypeScript base types with ones from OpenShift Dynamic Plugin SDK
• replace Console hooks with ones from OpenShift Dynamic Plugin SDK
  • useExtensions
  • useResolvedExtensions
  • useDynamicPluginInfo => usePluginInfo
  • useFlag => useFeatureFlag

Generated @openshift-console/dynamic-plugin-sdk package should be updated as follows:

• add dependency on @openshift/dynamic-plugin-sdk
• ensure consistent usage of TypeScript base types from OpenShift Dynamic Plugin SDK
• ensure that updated Console dynamic demo plugin builds and runs without any issues

@openshift/dynamic-plugin-sdk package should be updated as follows:

• feature discrepancies between console and openshift SDK are resolved and console-only features are forward-ported
• CI is fixed

Both Console and OpenShift Dynamic Plugin SDK should be updated to address any discrepancies.

AC:

• Console should use @openshift/dynamic-plugin-sdk package for plugin runtime infra
• Console dynamic demo plugin should be successfully built and working as before
• Crontab plugin should be successfully built and working as before