Skip to content
PR Build

fix(ecs): Alarms with custom dimensions should be processed #4569

Sign in to view logs

fix(ecs): Alarms with custom dimensions should be processed

fix(ecs): Alarms with custom dimensions should be processed #4569

Triggered via pull request December 23, 2024 14:52
@christosarvanitischristosarvanitis
opened #6324
armory-io:fix-ecs-alarms-custom-dimensions
Status Success
Total duration 33m 24s
Artifacts 3

pr.yml

on: pull_request
build
33m 12s
build
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build
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: Dockerfile.slim#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ECR_TOKEN_VERSION") 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: Dockerfile.slim#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ECR_TOKEN_VERSION") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
spinnaker~clouddriver~I7FF6O.dockerbuild
434 KB
spinnaker~clouddriver~NHLGBY.dockerbuild
71 KB
spinnaker~clouddriver~RV6ZB4.dockerbuild
24.7 KB