Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-26087: add snyk config file for SAST scan #95

Merged
merged 1 commit into from Jan 9, 2024

Conversation

gabemontero
Copy link
Contributor

Per the documented policy from ART for the SAST scans, and following the pattern established in the openshift/oc repo, we are introducing a snyk config file that excludes the vendor tree, as that is currently some minor warnings.

Per the documented policy from ART for the SAST scans, and following the pattern established in the openshift/oc repo, we are introducing a snyk config file that excludes the vendor tree, as that is currently some minor warnings.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 9, 2024
@openshift-ci-robot
Copy link

@gabemontero: This pull request references Jira Issue OCPBUGS-26087, 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 New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jitendar-singh

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

In response to this:

Per the documented policy from ART for the SAST scans, and following the pattern established in the openshift/oc repo, we are introducing a snyk config file that excludes the vendor tree, as that is currently some minor warnings.

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-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 9, 2024
Copy link
Contributor

openshift-ci bot commented Jan 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gabemontero

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2024
@gabemontero
Copy link
Contributor Author

/assign @coreydaley

@gabemontero
Copy link
Contributor Author

/assign @otaviof

@coreydaley
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2024
@gabemontero
Copy link
Contributor Author

non-related operators did not come up

/retest

Copy link
Contributor

openshift-ci bot commented Jan 9, 2024

@gabemontero: 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 7c069d8 link false /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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 00288a8 into openshift:master Jan 9, 2024
6 of 7 checks passed
@openshift-ci-robot
Copy link

@gabemontero: Jira Issue OCPBUGS-26087: All pull requests linked via external trackers have merged:

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

In response to this:

Per the documented policy from ART for the SAST scans, and following the pattern established in the openshift/oc repo, we are introducing a snyk config file that excludes the vendor tree, as that is currently some minor warnings.

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.

@gabemontero gabemontero deleted the snyk-cfg branch January 10, 2024 00:45
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-csi-driver-shared-resource-operator-container-v4.16.0-202401100232.p0.g00288a8.assembly.stream for distgit ose-csi-driver-shared-resource-operator.
All builds following this will include this PR.

@gabemontero
Copy link
Contributor Author

/cherrypick release-4.15

@openshift-cherrypick-robot

@gabemontero: new pull request created: #96

In response to this:

/cherrypick release-4.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants