Skip to content

fix: Treat 404 response status on Logto role removal as success #2759

fix: Treat 404 response status on Logto role removal as success

fix: Treat 404 response status on Logto role removal as success #2759

Triggered via push October 24, 2024 17:34
Status Success
Total duration 12m 13s
Artifacts 2

dispatch.yml

on: push
Lint  /  Broken Markdown links
3m 21s
Lint / Broken Markdown links
Lint  /  Super Linter
7m 0s
Lint / Super Linter
Build & Test  /  Build Node.js
11m 35s
Build & Test / Build Node.js
Build & Test  /  Build Docker image
5m 48s
Build & Test / Build Docker image
Release  /  Release Docker image
Release / Release Docker image
Fit to window
Zoom out
Zoom in

Annotations

15 warnings and 2 notices
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/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L107
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#L122
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#L81
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "VERIDA_PRIVATE_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#L82
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "POLYGON_PRIVATE_KEY") 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#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#L104
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#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#L112
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#L90
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "STRIPE_PUBLISHABLE_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Slow Test: [Logged In User Tests] › sequential/accreditation/issue-verify-flow.spec.ts#L1
[Logged In User Tests] › sequential/accreditation/issue-verify-flow.spec.ts took 2.3m
Slow Test: [Logged In User Tests] › sequential/accreditation/suspension-flow.spec.ts#L1
[Logged In User Tests] › sequential/accreditation/suspension-flow.spec.ts took 1.8m
Slow Test: [Logged In User Tests] › sequential/accreditation/revocation-flow.spec.ts#L1
[Logged In User Tests] › sequential/accreditation/revocation-flow.spec.ts took 1.2m
Slow Test: [Logged In User Tests] › sequential/credential/suspension-flow.spec.ts#L1
[Logged In User Tests] › sequential/credential/suspension-flow.spec.ts took 59.3s
Slow Test: [Logged In User Tests] › sequential/credential/revocation-flow.spec.ts#L1
[Logged In User Tests] › sequential/credential/revocation-flow.spec.ts took 36.8s
🎭 Playwright Run Summary
4 skipped 61 passed (2.2m)
🎭 Playwright Run Summary
20 passed (7.1m)

Artifacts

Produced during runtime
Name Size
cheqd~studio~V7QCVM.dockerbuild Expired
55.4 KB
studio-staging Expired
706 MB