Workflow Dispatch

feat: Add resource connector in credential issuance #2592

Sign in to view logs

Triggered via push September 23, 2024 07:53

DaevMithran

develop

Status Failure

Total duration 6m 52s

Artifacts 2

dispatch.yml

on: push

Lint / Broken Markdown links

Lint / Super Linter

Build & Test / Build Node.js

Build & Test / Build Docker image

Release / Semantic Release

Staging / Staging Deploy

Release / Release Docker image

Annotations

2 errors and 10 warnings

Build & Test / Build Node.js

Error: Process from config.webServer was not able to start. Exit code: 1

Build & Test / Build Node.js

Process completed with exit code 1.

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L94

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L99

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L113

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L115

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L143

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L106

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "EXTERNAL_DB_ENCRYPTION_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L127

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "API_KEY_EXPIRATION") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L135

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L141

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Sensitive data should not be used in the ARG or ENV commands: docker/Dockerfile#L91

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "STRIPE_WEBHOOK_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime

Name	Size
cheqd~studio~VV1ITJ.dockerbuild	59.5 KB
studio-staging	705 MB