+++ This bug was initially created as a clone of Bug #1796185 +++
Description of problem:
When selecting to add a pipeline from a runtime in the Add flows, it negates the understanding of the resource type that the pipeline may be in reference to.
Version-Release number of selected component (if applicable):
Noticed in 4.4, will need to be put back into 4.3.
Steps to Reproduce:
1. Once a Pipeline is added to the `openshift` namespace with the appropriate label tying it to a runtime (ie pipeline.openshift.io/runtime:java - for the java runtime)
2. Navigate to the +Add flow and import from Git (or Dockerfile)
3. Notice that selecting the java runtime gets you the associated pipeline from the `openshift` namespace
4. Change your Resource type (Deployment, Deployment Config, Knative - if installed) and the pipeline is unaffected
Unable to associate a pipeline that may include internals for deployment vs knative for instance.
Being able to associate a pipeline to both a runtime as well as a resource type.
Logged first here https://issues.redhat.com/browse/ODC-2880 but needs backport to 4.3
Created attachment 1667265 [details]
Enable pipelines for Knative and Kubernetes apps on import
Created attachment 1671274 [details]
Enable pipelines for Knative and Kubernetes apps on import-1
Created attachment 1671275 [details]
Enable pipelines for Knative and Kubernetes apps on import-2
Verified on build: 4.3.0-0.ci-2020-03-16-190421
Chrome browser: 76.0.3809.132
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.