snyk: exclude vendor/

[2uasimojo]

...as we expect vulns in deps to be caught by the dep scan.

[2uasimojo]

/assign @dlom

This is working. security fail is expected at this point:

• grpc dep update still needed.
• low/med exclusions coming via release repo PR.

[dlom]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,dlom]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 792dfb6 and 2 for PR HEAD f3f64d4 in total

[openshift-ci]

@2uasimojo: 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	f3f64d4	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.

[2uasimojo]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@2uasimojo: new pull request could not be created: failed to create pull request against openshift/cloud-credential-operator#release-4.16 from head openshift-cherrypick-robot:cherry-pick-613-to-release-4.16: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.16 and openshift-cherrypick-robot:cherry-pick-613-to-release-4.16"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-4.16

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.

[2uasimojo]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@2uasimojo: new pull request could not be created: failed to create pull request against openshift/cloud-credential-operator#release-4.15 from head openshift-cherrypick-robot:cherry-pick-613-to-release-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.15 and openshift-cherrypick-robot:cherry-pick-613-to-release-4.15"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick 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.

[2uasimojo]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@2uasimojo: new pull request created: #615

In response to this:

/cherry-pick release-4.14

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.