Skip to content

feat(api): Ensure that the project scorecards are wiped before new on… #238

feat(api): Ensure that the project scorecards are wiped before new on…

feat(api): Ensure that the project scorecards are wiped before new on… #238

Triggered via push January 12, 2025 14:21
Status Success
Total duration 5m 3s
Artifacts 1

deploy.yml

on: push
Set Environment
0s
Set Environment
trigger_build
3s
trigger_build
Build Client image and push to Amazon ECR
0s
Build Client image and push to Amazon ECR
Build API image and push to Amazon ECR
1m 18s
Build API image and push to Amazon ECR
Build Backoffice image and push to Amazon ECR
0s
Build Backoffice image and push to Amazon ECR
Deploy Services to Amazon EBS
3m 14s
Deploy Services to Amazon EBS
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
trigger_build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Set Environment
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#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#L29
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#L7
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "DB_PASSWORD") 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/
Sensitive data should not be used in the ARG or ENV commands: api/Dockerfile#L21
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "BACKOFFICE_SESSION_COOKIE_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#L29
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ACCESS_TOKEN_EXPIRES_IN") 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#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#L38
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#L40
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#L9
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "ACCESS_TOKEN_EXPIRES_IN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Deploy Services to Amazon EBS
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy Services to Amazon EBS
Environment update finished, but health is Yellow and health status is Warning. Giving it 30 seconds to recover...
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~2CC3JL.dockerbuild
55.1 KB