Skip to content

Load datacatalog config into propeller even when datacatalog deployme… #7694

Load datacatalog config into propeller even when datacatalog deployme…

Load datacatalog config into propeller even when datacatalog deployme… #7694

Triggered via push June 2, 2026 17:22
Status Success
Total duration 16m 20s
Artifacts 7
test-bootstrap
1m 6s
test-bootstrap
build-and-push-single-binary-image
7m 22s
build-and-push-single-binary-image
sandbox-bundled-functional-tests
7m 43s
sandbox-bundled-functional-tests
sandbox-bundled-offloaded-functional-tests
7m 23s
sandbox-bundled-offloaded-functional-tests
build-and-push-sandbox-bundled-image
3m 9s
build-and-push-sandbox-bundled-image
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
test-bootstrap
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-push-single-binary-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/login-action@v2, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-push-single-binary-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-single-binary-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-single-binary-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-single-binary-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-single-binary-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-sandbox-bundled-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v2, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-push-sandbox-bundled-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-sandbox-bundled-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-sandbox-bundled-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-sandbox-bundled-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-and-push-sandbox-bundled-image
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
sandbox-bundled-offloaded-functional-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-python@v4, docker/build-push-action@v6, docker/setup-buildx-action@v2, unionai/flytectl-setup-action@v0.0.3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
sandbox-bundled-functional-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-python@v4, docker/build-push-action@v6, docker/setup-buildx-action@v2, unionai/flytectl-setup-action@v0.0.3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
flyteorg~flyte~2F2YGX.dockerbuild
56.7 KB
sha256:71a441f2718166d725abb9ea277cf07948dcaa9ab60208ea5a556a81a88d1d47
flyteorg~flyte~2P0J33.dockerbuild
73.8 KB
sha256:4f1cda96ccec3eb85a15a2387983d99a166f3e0a7ae5d7a4b1c014aa439c4e8b
flyteorg~flyte~JLXJP1.dockerbuild
74.4 KB
sha256:c253b00edf3af6e80d0697b7b00c5ef8907691acd37d020f7e6f331a045557a1
flyteorg~flyte~P0XBG6.dockerbuild
79.3 KB
sha256:29d948f81fb8e3e5cd2fcb02060aebe11c49893be66d2547ba208483675326aa
flyteorg~flyte~Q1HSPH.dockerbuild
125 KB
sha256:3df82ff942b9b08fa5fe055f2f93147559b9f7f915ec26f95ee6e52d1a98af6d
flyteorg~flyte~WWX6CC.dockerbuild
92.6 KB
sha256:9e6faf42c5bf741e4c6c9a5e766f52368e3b1bab0ac88886bfcfa30f702b4d87
single-binary-image
190 MB
sha256:df326ac168316eb3d5d7625feb96efc8bc8610f80d4baffe9c438e9191424b81