Description of problem:

The structured logs for Pipelines as Code miss important source repository details from the initiating webhook request. Such information would make it easier for operators to identify user-reported issues.

Workaround: Grepping of individual log files

Prerequisites (if any, like setup, operators/versions):

OpenShift Pipelines on Konflux (latest?)

Steps to Reproduce

Run a Pipeline with Pipelines as Code
 

Actual results:

The "pac-watcher" and "pac-controller" logs contain an `event-sha` key that contains the commit ID for the webhook event. It does not contain other information reporting the origin of the webhook event.

Expected results:

The pac-watcher and pac-controller logs should report enough context for an operator to identify where a webhook event came from, such as:

• Source repository URL
• Branch name, if provided
• Event type (this is not always consistent)
• Commit SHA (also not always consistent)

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *