fix(KONFLUX-3663): format PipelineRun files and upload SAST results

[ccronca]

This update configures the SAST task to upload SARIF results to quay.io for long-term storage

Please note that this PR was automatically generated and may include unrelated changes due to automatic YAML formatting performed by yq
The YAML files will be indented using 2 spaces, if the YAML file uses indentationless list the automation will try to keep this format

The PR contains two separate commits:

1. Format YAML files: Ensures consistent indentation and formatting of the YAML files
2. Upload SAST results: Configures the PipelineRun files to enable uploading SARIF results to quay.io

Separating these changes into two commits simplifies the review process. The first commit focuses on indentation and formatting, while the second commit contains the semantic changes

Related:

• https://issues.redhat.com/browse/KONFLUX-3663
• https://issues.redhat.com/browse/KONFLUX-2263

[openshift-ci]

Hi @ccronca. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[2uasimojo]

/ok-to-test
/approve
/assign @celebdor

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo, ccronca

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [2uasimojo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ccronca]

/retest

[ccronca]

@2uasimojo It looks like some security tests are failing, but they don't seem related to my change

[2uasimojo]

@2uasimojo It looks like some security tests are failing, but they don't seem related to my change

Yeah, that’s being addressed via #2387 – though it’s not going particularly well 😬

In any case, not part of this issue.

/override ci/prow/security

[openshift-ci]

@2uasimojo: Overrode contexts on behalf of 2uasimojo: ci/prow/security

In response to this:

@2uasimojo It looks like some security tests are failing, but they don't seem related to my change

Yeah, that’s being addressed via #2387 – though it’s not going particularly well 😬

In any case, not part of this issue.

/override ci/prow/security

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

@ccronca: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	31ab29f	link	true	/test security

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ccronca]

@2uasimojo Btw, it looks like the hive-mce-25-on-pull-request check is failing. The issue seems to be with the clamav-scan task validation. I believe the image for this taskref bundle needs to be updated. This thread has some information about it

[2uasimojo]

@celebdor really needs to weigh in there. ISTR him talking about ripping konflux out of 2.5 anyway...?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale