Skip to content

Chore: Remove tests #541

Chore: Remove tests

Chore: Remove tests #541

Triggered via pull request September 4, 2024 18:52
Status Success
Total duration 15s
Artifacts

auto.yml

on: pull_request
Run terraform fmt
4s
Run terraform fmt
Run terraform-lint
5s
Run terraform-lint
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Run terraform fmt
The following actions uses node12 which is deprecated and will be forced to run on node16: hashicorp/setup-terraform@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run terraform fmt
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab, hashicorp/setup-terraform@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run terraform fmt
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/
Run terraform fmt
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/
Run terraform fmt
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/
Run terraform-lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@8e5e7e5ab8b370d6c329ec480221332ada57f0ab, terraform-linters/setup-tflint@ba6bb2989f94daf58a4cc6eac2c1ca7398a678bf. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/