Run deploy

Fix implementation labor type problem #180

Sign in to view logs

Triggered via push December 17, 2024 09:13

dev

Status Success

Total duration 1m 26s

Artifacts 1

deploy.yml

on: push

Set Environment

Build Client image and push to Amazon ECR

Build API image and push to Amazon ECR

Build Backoffice image and push to Amazon ECR

Deploy Services to Amazon EBS

Annotations

13 warnings

Set Environment

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

trigger_build

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Build API image and push to Amazon ECR

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SES_ACCESS_KEY_ID") 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: api/Dockerfile#L25

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: api/Dockerfile#L27

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DB_PASSWORD") 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: api/Dockerfile#L28

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: api/Dockerfile#L35

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: api/Dockerfile#L8

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "ACCESS_TOKEN_SECRET") 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: api/Dockerfile#L10

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "RESET_PASSWORD_TOKEN_SECRET") 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: api/Dockerfile#L31

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: api/Dockerfile#L41

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: api/Dockerfile#L36

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/

Artifacts

Produced during runtime

Name	Size
Vizzuality~tnc-blue-carbon-cost-tool~CHWLCO.dockerbuild	54.1 KB