infrastructure-as-code

Terraform Version

Terraform v1.2.2
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.18.0
+ provider registry.terraform.io/hashicorp/random v3.3.1
+ provider registry.terraform.io/mongey/kafka v0.5.1
+ provider registry.terraform.io/scottwinkler/shell v1.7.10

Git version

git version 2.25.4

Terraform Configuration Files

1. This works, b

currently we have a version selector for every git tag, which is unnecessary overhead on the user. It is not needed from documentation perspective as there aren't (shouldn't be) any docs change in patch versions, only for new/changed features.

before:
v0.27.0, v0.27.1, v0.27.2, v0.28.0
after
v0.27, v0.28

Description
I tried to use the state aptpkg.held as shown in the documentation, only for that state to apparently not exist.

I tried looping through state modules such as apt, pkg, and aptpkg with hold and held states, to find apt.held as the actually correct usage.

$ for major in apt pkg ap

Describe the bug

I have written a simple integration test case to my stack in Python, but I am not able to run it. I used integ-runner and tried with cdk deploy --app "python integration_test.py" but it seems none of them are working. Is this feature available only with ts library?

Many thanks

Expected Behavior

Able to run my tests.

Current Behavior

yarn's integ-runner cli us

Infracost comment is showing the "Module path" column even though it's empty.

Expected result:
If "Module path" is column is empty it should be hidden

Issue
If it is related to an existing check, CKV_DOCKER_1.
Dockerfile EXPOSE can accept port using tcp proto by defaut if not specified or you can also specify the protocol with /tcp or /udp.

When using "EXPOSE 22/tcp" the rule does not detect the SSH port. something like '22/tcp'.split('/')[0] will return port without protocol or we can test both '22' or '22/tcp' in the rule.

**Exampl

• terrascan version: 1.9.0
• terraform version: 1.0.1

Enhancement Request

Other security scanning tools (e.g. checkov and tfsec) have a --soft-fail flag or equivalent option that allows you to always exit with 0 status.

Extremely useful when running the tool without halting a pipeline for example.

I currently use a workaround, but something more concrete would be very desira

The --prod flag has been deprecated, so we should not show that field in the output of the env show command, or in our docs:

https://aws.github.io/copilot-cli/docs/concepts/environments/
https://aws.github.io/copilot-cli/docs/commands/env-show/

Description

We discovered with @wbeuil that when creating an aws_eip resource without a eip association, refreshing the state adds a association ID to it, since an association has been cre