Skip to content
Destroy Expired Environment

Destroy Expired Environment #125

Sign in to view logs

Destroy Expired Environment

Destroy Expired Environment #125

Triggered via schedule October 5, 2024 00:24
@gurevichdmitrygurevichdmitry
⁠ 81401f9
main
Status Failure
Total duration 5m 49s
Artifacts –

destroy-expired-environment.yml

on: schedule
envs_to_destroy
2m 25s
envs_to_destroy
Matrix: destroy_environment
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
destroy_environment (sean-agentless-4) / Destroy
Process completed with exit code 1.
destroy_environment (tin-demo) / Destroy
Process completed with exit code 1.
envs_to_destroy
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
destroy_environment (sean-agentless-4) / Destroy
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, hashicorp/[email protected], slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
destroy_environment (tin-demo) / Destroy
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, hashicorp/[email protected], slackapi/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/