Goal:

Convert Pipelines from a static to a dynamic plugin, while keeping it in the mono repo (thus the delivery mechanism will remain the same).

All internal dependencies should be identified and evaluated to see what needs to be supported by the SDK. Once this epic is complete, the Pipelines plugin should no longer have any internal dependencies.

Why is it important?

Our end goal is to have a fully featured SDK which supports dynamic plugins. In the future, we hope to have the Pipelines dynamic plugin be delivered via the operator to (a) minimize dependencies between the operator and console and (b) enable users to get access to the pipeline UI bits as the operator and features are enabled rather than waiting for the next OpenShift release.

Acceptance criteria:

1. Internal dependencies are identified and either removed or moved to the SDK
2. Existing static plugin is converted to a dynamic plugin

Dependencies (External/Internal):

Note: