OCPBUGS-26124,OCPBUGS-27861: update snyk file

[elmiko]

This change is reacting to a recent sast scan, it ensures that we are skipping files which are not included in our builds and releases.

[openshift-ci-robot]

@elmiko: This pull request references Jira Issue OCPBUGS-26124, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This change is reacting to a recent sast scan, it ensures that we are skipping files which are not included in our builds and releases.

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 openshift-eng/jira-lifecycle-plugin repository.

[JoelSpeed]

/approve
/lgtm

[elmiko]

/title OCPBUGS-26124,OCPBUGS-27861: update snyk file

[openshift-ci-robot]

@elmiko: This pull request references Jira Issue OCPBUGS-26124, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27861, which is invalid:

• expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This change is reacting to a recent sast scan, it ensures that we are skipping files which are not included in our builds and releases.

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 openshift-eng/jira-lifecycle-plugin repository.

[racheljpg]

/jira refresh

[openshift-ci-robot]

@racheljpg: This pull request references Jira Issue OCPBUGS-26124, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

This pull request references Jira Issue OCPBUGS-27861, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[JoelSpeed]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 [JoelSpeed]

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

[JoelSpeed]

/retest

[openshift-ci]

@elmiko: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@elmiko: Jira Issue OCPBUGS-26124: All pull requests linked via external trackers have merged:

• openshift/cloud-provider-vsphere#61
• openshift/cloud-provider-azure#107

Jira Issue OCPBUGS-26124 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27861: All pull requests linked via external trackers have merged:

• openshift/cloud-provider-azure#107

Jira Issue OCPBUGS-27861 has been moved to the MODIFIED state.

In response to this:

This change is reacting to a recent sast scan, it ensures that we are skipping files which are not included in our builds and releases.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-azure-cloud-node-manager-container-v4.16.0-202402231839.p0.g494bc60.assembly.stream.el9 for distgit ose-azure-cloud-node-manager.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-02-26-013420