Description of problem:
In Add trigger form, Git provider type dropdown lists TriggerBindings and ClusterTriggerBindings without resource badges which makes it difficult for the user to distinguish
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a pipeline
2. click on Add trigger option in the pipeline page actions.
In Git type provider dropdown, TriggerBindings and ClusterTriggerBindings are shown without any badges.
The dropdown items should contain the resource badges to differntiate the resource based on the kind.
verified on build 4.6.0-0.nightly-2020-09-25-085318
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.