When on the EventListener Details page, UX designed the URL to appear under the TriggerTemplate reference (mimicking what we used in the Pipeline details page). This made a lot of sense at the time and was agreed to by dev and PM. However, upon investigating the usage of ClusterTriggerBindings, I noticed that there is a potential issue here. If there are multiple TriggerTemplates on a given EventListener, the URL likely is to repeat for each one... as the EventListener is actually the originator of the URL (a Route object is technically the owner), not the TriggerTemplate. This is misleading and can result in a duplicate rendering in the UI. My suggestion on the design doc was to use a Route object resource link... but Siamak Sadeghianfar made a valid point of "the user is more interested in the URL itself, not the Route object" and thus leaves us with figuring out what the design will be. Acceptance Criteria In short, this is what needs to be done: - Remove the URL from under the TriggerTemplate, it's not related to this resource - Discuss with UX about the best way to show this information - Render the link on the details page Suggested Design Ideas - Link to the Route object - Show the URL under it's own section at the top of the right-side details; something like "URL" title with the URL under it
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