Deploy to Dev

Use initial carbon price assumption #22

Sign in to view logs

Triggered via push January 30, 2025 10:24

alexeh

dev

Status Success

Total duration 5m 33s

Artifacts 1

deploy-dev.yml

on: push

deploy / trigger_build

deploy / Build Client image and push to Amazon ECR

deploy / Build API image and push to Amazon ECR

deploy / Build Backoffice image and push to Amazon ECR

deploy / Deploy Services to Amazon EBS

Annotations

12 warnings

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

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "EMAIL_CONFIRMATION_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#L17

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AWS_SES_ACCESS_KEY_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#L24

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#L26

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#L34

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#L37

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#L14

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "ACCOUNT_CONFIRMATION_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#L27

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#L37

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "AWS_SES_ACCESS_KEY_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/

deploy / Deploy Services to Amazon EBS

Environment update finished, but health is Yellow and health status is Warning. Giving it 30 seconds to recover...

deploy / Deploy Services to Amazon EBS

Environment still has health: Yellow and health status Warning. Waiting 19 more seconds before failing...

Artifacts

Produced during runtime

Name	Size
Vizzuality~tnc-blue-carbon-cost-tool~1AE2XB.dockerbuild	55.2 KB