Skip to content
.github/workflows/scans_ci.yml

.github/workflows/scans_ci.yml #653

Sign in to view logs

.github/workflows/scans_ci.yml

.github/workflows/scans_ci.yml #653

Triggered via create August 31, 2024 21:14
@ekmixonekmixon
⁠ 3e336e5
Status Failure
Total duration 21s
Artifacts –

scans_ci.yml

on: create
build
12s
build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
build: plugins/google/deploymentmanager/deleteExpiredDeployments.js#L16
depoyment ==> deployment
build: plugins/google/sql/postgresqlLogCheckpoints.js#L52
PosgreSQL ==> postgresql
build: plugins/google/iam/serviceAccountKeyRotation.js#L16
accoun ==> account
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
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/
build
The following actions use a deprecated Node.js version 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/