Description of problem: In the EventListener spec there is a property called "triggers" which can have 1 to n TriggerBindings and a single TriggerTemplate associated to it. Currently we do not have a good way to represent this. We flatten the content today, and it's a bit misleading. We need to be able to nest / group these resources together better. Version-Release number of selected component (if applicable): 4.6 How reproducible: Always Steps to Reproduce: 1. Create Event Listener apiVersion: triggers.tekton.dev/v1alpha1 kind: EventListener metadata: name: event-listener-test spec: serviceAccountName: pipeline triggers: - bindings: - kind: ClusterTriggerBinding name: github-pullreq template: name: trigger-template-nodejs-rest-http-chz9v1 - bindings: - kind: ClusterTriggerBinding name: bitbucket-pullreq - kind: ClusterTriggerBinding name: bitbucket-commit template: name: trigger-template-nodejs-rest-http-abc123 2. Goto Event Listener Details page. Actual results: Trigger Templates & Trigger Bindings/ClusterTriggerBindings are listed separately Expected results: The resources should be nested Additional info:
Created attachment 1716144 [details] EventListener Details page represents "Trigger" groupings
Verify on build version: 4.6.0-0.nightly-2020-09-22-130743 Browser version: Chrome 84
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. https://access.redhat.com/errata/RHBA-2020:4196