Skip to content

feat(deps): bump actions/setup-go from 5.1.0 to 5.2.0 #551

feat(deps): bump actions/setup-go from 5.1.0 to 5.2.0

feat(deps): bump actions/setup-go from 5.1.0 to 5.2.0 #551

Triggered via pull request December 11, 2024 12:19
Status Success
Total duration 51s
Artifacts

test.yaml

on: pull_request
terraform-valid  /  Config Validation in ./test/terraform
24s
terraform-valid / Config Validation in ./test/terraform
trivy-invalid  /  Config Validation in ${{ inputs.working-directory }}
0s
trivy-invalid / Config Validation in ${{ inputs.working-directory }}
terraform-valid  /  Trivy Vulnerability Scan in ./test/terraform
9s
terraform-valid / Trivy Vulnerability Scan in ./test/terraform
terraform-valid  /  Generate SBOM in ${{ inputs.working-directory }}
0s
terraform-valid / Generate SBOM in ${{ inputs.working-directory }}
trivy-invalid  /  Trivy Vulnerability Scan in ./test/trivy
14s
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy
trivy-invalid  /  Generate SBOM in ${{ inputs.working-directory }}
0s
trivy-invalid / Generate SBOM in ${{ inputs.working-directory }}
terraform-valid  /  Render terraform docs in ./test/terraform
11s
terraform-valid / Render terraform docs in ./test/terraform
trivy-invalid  /  Render terraform docs in ${{ inputs.working-directory }}
0s
trivy-invalid / Render terraform docs in ${{ inputs.working-directory }}
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 6 warnings
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L37
AVD-AWS-0005: API Gateway domain name uses outdated SSL/TLS protocols. You should not use outdated/insecure TLS versions for encryption. You should be using TLS v1.2+. Domain name is configured with an outdated TLS policy. Resolution: Use the most modern TLS/SSL policies available https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-custom-domain-tls-version.html https://avd.aquasec.com/misconfig/avd-aws-0005
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L33
AVD-AWS-0005: API Gateway domain name uses outdated SSL/TLS protocols. You should not use outdated/insecure TLS versions for encryption. You should be using TLS v1.2+. Domain name is configured with an outdated TLS policy. Resolution: Use the most modern TLS/SSL policies available https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-custom-domain-tls-version.html https://avd.aquasec.com/misconfig/avd-aws-0005
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L41
AVD-AWS-0005: API Gateway domain name uses outdated SSL/TLS protocols. You should not use outdated/insecure TLS versions for encryption. You should be using TLS v1.2+. Domain name is configured with an outdated TLS policy. Resolution: Use the most modern TLS/SSL policies available https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-custom-domain-tls-version.html https://avd.aquasec.com/misconfig/avd-aws-0005
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L20
AVD-AWS-0054: Use of plain HTTP. Plain HTTP is unencrypted and human-readable. This means that if a malicious actor was to eavesdrop on your connection, they would be able to see all of your data flowing back and forth.
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L23
AVD-AWS-0081: AWS Classic resource usage. AWS Classic resources run in a shared environment with infrastructure owned by other AWS customers. You should run
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L15
AVD-AWS-0107: An ingress security group rule allows traffic from /0. Opening up ports to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that explicitly require it where possible. Security group rule allows ingress from public internet. Resolution: Set a more restrictive cidr range https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html https://avd.aquasec.com/misconfig/avd-aws-0107
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy: main.tf#L29
AVD-AZU-0038: Enable disk encryption on managed disk Manage disks should be encrypted at rest. When specifying the <code>encryption_settings</code> block, the enabled attribute should be set to <code>true</code>. Managed disk is not encrypted. Resolution: Enable encryption on managed disks https://docs.microsoft.com/en-us/azure/virtual-machines/linux/disk-encryption https://avd.aquasec.com/misconfig/avd-azu-0038
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy
Process completed with exit code 1.
terraform-valid / Trivy Vulnerability Scan in ./test/terraform
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
trivy-invalid / Trivy Vulnerability Scan in ./test/trivy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
terraform-valid / Config Validation in ./test/terraform
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
terraform-valid / Config Validation in ./test/terraform
Restore cache failed: Dependencies file is not found in /home/runner/work/github-workflow-terraform-config/github-workflow-terraform-config. Supported file pattern: go.sum
terraform-valid / Render terraform docs in ./test/terraform
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
terraform-valid / Render terraform docs in ./test/terraform
The `python-version` input is not set. The version of Python currently in `PATH` will be used.