Skip to content
Terraform Validation

Use Nitro-based instance type in AWS for SLO discovery #329

Sign in to view logs

Use Nitro-based instance type in AWS for SLO discovery

Use Nitro-based instance type in AWS for SLO discovery #329

Triggered via pull request November 14, 2024 15:34
@rafael-mendes-pereirarafael-mendes-pereira
opened #390
rafaelme/change_machine
Status Success
Total duration 2m 13s
Artifacts –

terraform-validation.yml

on: pull_request
Setup terraform plan matrix for test scenarios
6s
Setup terraform plan matrix for test scenarios
terraform-validation
23s
terraform-validation
Matrix: terraform-plan
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
terraform-validation
The following actions use a deprecated Node.js version and will be forced to run on node20: hashicorp/setup-terraform@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
aws-perf-eval-apiserver-vn100pod10k
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-apiserver-vn100pod3k
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-apiserver-vn10pod100
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-cilium-cluster-churn-n1000p50k
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-cas-c4n10p100
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-nap-c4n10p100
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
aws-perf-eval-slo-servicediscovery
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, 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/
azure-perf-eval-slo-servicediscovery
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/