Apply Ocean version 0.10.9 to all integrations (#992) #860
Tankilevitch
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
54 warnings
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
integrations/_infra/Dockerfile#L8
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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
integrations/_infra/Dockerfile#L23
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
port-labs~ocean~9E57IU.dockerbuild
Expired
|
68.4 KB |
sha256:23a5c135537d1e2e0f34eedcdbb4ca3288f81f04a13eff74d46d503d921a56bc
|
|
|
port-labs~ocean~A7ODIQ.dockerbuild
Expired
|
67.7 KB |
sha256:4e3d120e0657759cfe1d9245ca3e7e30876884028c7c3315b1d0a1ee39373a4e
|
|
|
port-labs~ocean~B223GR.dockerbuild
Expired
|
68.9 KB |
sha256:3c097b5767ce2a5f7d39be38cc5989f8be31fccbdd946f5534526022022611a6
|
|
|
port-labs~ocean~B676JW.dockerbuild
Expired
|
67.7 KB |
sha256:0c1e5755296e01e308af7152c9aaea9638cadf13725cdd9938a2990d0f9258f9
|
|
|
port-labs~ocean~CDEFR1.dockerbuild
Expired
|
68 KB |
sha256:9d0b889ee3670a3463cf5ebd6447e254c6cbcbe67a574e2f46d799ff07112b61
|
|
|
port-labs~ocean~EN8YAU.dockerbuild
Expired
|
67.2 KB |
sha256:d2ea34c3fb200da9efe8abf54e12ea4024f296ea9fae24f7693416a8180edb1c
|
|
|
port-labs~ocean~EWPLT2.dockerbuild
Expired
|
67.7 KB |
sha256:26139eb69a01d81918018bd17a33f5a656e767a582644ad794e11520a6d3009d
|
|
|
port-labs~ocean~GZ60VL.dockerbuild
Expired
|
69.9 KB |
sha256:f52bd21a41fe0994f5f21d050f126550efe9f387df053b1792990513426a1006
|
|
|
port-labs~ocean~HA37O7.dockerbuild
Expired
|
67.1 KB |
sha256:d8ee255846efb37956ca771b29442b053d464d0d56d612c81b2dbfb396681669
|
|
|
port-labs~ocean~JP1WG3.dockerbuild
Expired
|
67.9 KB |
sha256:62e70363a7d3ca3b932624a6c85e65bf129d0ace6d8dff7db4af4d8a28fb8a13
|
|
|
port-labs~ocean~JPVDR2.dockerbuild
Expired
|
67.7 KB |
sha256:53f4f1e30c5e24182eb952e9d270d5442f561bd3ff13a739b74489afd5736ff2
|
|
|
port-labs~ocean~LKGW1D.dockerbuild
Expired
|
68.4 KB |
sha256:526165e4a20546bf0d3fe1ef6b47ac3c722ba0f7008cff57f4c4b0c6196fd559
|
|
|
port-labs~ocean~M0OQT2.dockerbuild
Expired
|
67.7 KB |
sha256:932ee90ba8c590faa00481febd58286509581bb7ab13a34b326c542b580c1f5e
|
|
|
port-labs~ocean~M0PRAC.dockerbuild
Expired
|
69.2 KB |
sha256:3e13b4b4407ce53eac3a5a915bbe6bb8dbc5e51ccceccfe33de2f8f153e90aa5
|
|
|
port-labs~ocean~MXUJXH.dockerbuild
Expired
|
68.5 KB |
sha256:6009c7db78fcb0dd6c2ec59b1a58ea9474b174f450aadac404ad0d9d6770b8a9
|
|
|
port-labs~ocean~MY0TL4.dockerbuild
Expired
|
68.2 KB |
sha256:b83a77c67f29da950582d04b06e9caf963cfe9535e7233993a8dc5cb667dedd5
|
|
|
port-labs~ocean~OAJIGF.dockerbuild
Expired
|
67.5 KB |
sha256:ffa2613507ea4e332ad28c1ec259442af879f454be12d6558e4bfb8706134be1
|
|
|
port-labs~ocean~OKF6XJ.dockerbuild
Expired
|
67.9 KB |
sha256:3040f00af659aa9a707573b0fdb102c42affcac3df2865bdfc964fd6a6dec5b0
|
|
|
port-labs~ocean~OREET5.dockerbuild
Expired
|
67.7 KB |
sha256:0f681410284a88696414277df62c94862906086b1bcc31a703b49df64f3593cf
|
|
|
port-labs~ocean~PGEBSJ.dockerbuild
Expired
|
67.5 KB |
sha256:28d43857c1c47b249340fbc68cd2ba78a8be175dd96513f8c73feab3af8c7918
|
|
|
port-labs~ocean~SDN7MT.dockerbuild
Expired
|
67.5 KB |
sha256:d918d0ee2586fe7e07a02bc65997a5d58a7d6243e96e317292a9d6cd85466ac5
|
|
|
port-labs~ocean~TKVXS5.dockerbuild
Expired
|
68.1 KB |
sha256:c3530b4b4811d8aa410b3835182972428693bc195d9f019e121a33d61ec43dd4
|
|
|
port-labs~ocean~UB2V3O.dockerbuild
Expired
|
68.5 KB |
sha256:e1c1867b67b3256da0cf149c92227d9d684b6a94690ee65e1486adb89ae64a47
|
|
|
port-labs~ocean~VQ1IR8.dockerbuild
Expired
|
68 KB |
sha256:cbf08e2bc0b417ee2214341aa5a3115cd8188bd5d55b9e28a5c7fcc95ad1771a
|
|
|
port-labs~ocean~Y3NXBU.dockerbuild
Expired
|
68 KB |
sha256:2c2b2242739246bf998753fe00577e1911b11a87edec24b9f92533863e660d7d
|
|
|
port-labs~ocean~YG66BM.dockerbuild
Expired
|
68 KB |
sha256:76e299223a630d3fa350eb42f385c77e94158c016be9cc348ac9bd16aaced199
|
|
|
port-labs~ocean~ZD34V4.dockerbuild
Expired
|
67.7 KB |
sha256:bb9ca72f5f7758c6cecdc2e661d7b5c1fd9393347c7c6d87128b7185e3df7909
|
|