.github/workflows/scans_ci.yml

Merge pull request #1430 from abdullahaslam306/feature/SAAS-9853-aws-… #620

Sign in to view logs

Summary
Jobs
- build
Run details
- Usage
- Workflow file

Triggered via push July 18, 2024 05:16

ekmixon

snyk-upgrade-fb7c93871dbd0c5e5a313a231d052b2b

Status Failure

Total duration 20s

Artifacts –

scans_ci.yml

on: push

Annotations

6 errors and 2 warnings

build: plugins/azure/virtualnetworks/virtualNetworkPeering.js#L84

Vitual ==> Virtual, Visual

build: plugins/aws/elasticache/elasticacheInstanceGeneration.js#L12

generaion ==> generation

build: plugins/aws/sns/snsValidSubscribers.js#L9

subsribers ==> subscribers

build: plugins/google/iam/serviceAccountKeyRotation.js#L16

accoun ==> account

build: plugins/google/deploymentmanager/deleteExpiredDeployments.js#L16

depoyment ==> deployment

build: plugins/google/sql/postgresqlLogCheckpoints.js#L52

PosgreSQL ==> postgresql

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/