Bug 1875599 - OpenShift Dev ConsoleODC-3710 EventListener Details page needs to represent "Trigger" groupings
Summary: OpenShift Dev ConsoleODC-3710 EventListener Details page needs to represent "...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.6.0
Assignee: Debsmita Santra
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-03 20:39 UTC by Debsmita Santra
Modified: 2020-10-27 16:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:37:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
EventListener Details page represents "Trigger" groupings (80.61 KB, image/png)
2020-09-23 21:02 UTC, spathak@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6518 0 None closed Bug 1875599: trigger groupings in Event Listener details page 2020-09-23 13:31:34 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:38:04 UTC

Description Debsmita Santra 2020-09-03 20:39:39 UTC
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:

Comment 2 spathak@redhat.com 2020-09-23 21:02:23 UTC
Created attachment 1716144 [details]
EventListener Details page represents "Trigger" groupings

Comment 3 spathak@redhat.com 2020-09-23 21:03:25 UTC
Verify on build version: 4.6.0-0.nightly-2020-09-22-130743
Browser version: Chrome 84

Comment 6 errata-xmlrpc 2020-10-27 16:37:51 UTC
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


Note You need to log in before you can comment on or make changes to this bug.