chore: expose ecs outputs to consumers #295
odunloppr.yml
on: pull_request
Terraform-Format
5s
KICS Scan
43s
Annotations
17 warnings
|
Terraform-Format
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
|
Terraform-Format
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
|
Terraform-Format
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/
|
|
Terraform-Format
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/
|
|
Terraform-Format
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/
|
|
KICS Scan
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
KICS Scan
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
[LOW] Autoscaling Groups Supply Tags:
repo/modules/ec2/main.tf#L219
Autoscaling groups should supply tags to configurate
|
|
[INFO] Resource Not Using Tags:
repo/modules/ecs/main.tf#L205
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/subnets/main.tf#L23
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/ec2/main.tf#L219
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/ec2/main.tf#L197
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/database/security_groups.tf#L5
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/database/rds.tf#L47
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/ecs/main.tf#L183
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/ecs/main.tf#L150
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|
|
[INFO] Resource Not Using Tags:
repo/modules/security_groups/main.tf#L5
AWS services resource tags are an essential part of managing components. As a best practice, the field 'tags' should have additional tags defined other than 'Name'
|