You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It works fine if we pin commenter to 1.2.0, but the latest (1.3.1) is acting weird. Here's an example of logs:
+ tfsec --out=results.json --format=json --soft-fail --soft-fail terraform/aws/develop/shared
1 file(s) written: results.json
+ commenter
Starting the github commenter
Working in repository terraform
Working in PR 9999
TFSec found 21 issues
Working in GITHUB_WORKSPACE /github/workspace/
Preparing comment forviolation of rule aws-ec2-enable-at-rest-encryptionin terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf
Ignoring - change not part of the current PR
Preparing comment forviolation of rule aws-ec2-enable-at-rest-encryptionin terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf
Ignoring - change not part of the current PR
Preparing comment forviolation of rule aws-ec2-enforce-http-token-imdsin terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf
Ignoring - change not part of the current PR
Preparing comment forviolation of rule aws-ec2-enforce-http-token-imdsin terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf
Ignoring - change not part of the current PR
# blablabla and they all are ignored!
It appaers to append the working directory to filename twice! For example, terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf should be terraform/aws/develop/shared/test.tf.
The text was updated successfully, but these errors were encountered:
hi-artem
changed the title
1.3.0 Upgrade is Breaking Pipeline with Custom working_directory
1.3.x Upgrade is Breaking Pipeline with Custom working_directoryNov 3, 2022
We have a huge monorepo with multiple entrypoints for Terraform. The 1.3.x release is breaking our pipeline.
The example of pipeline:
It works fine if we pin
commenter
to 1.2.0, but the latest (1.3.1) is acting weird. Here's an example of logs:It appaers to append the working directory to filename twice! For example,
terraform/aws/develop/shared/terraform/aws/develop/shared/test.tf
should beterraform/aws/develop/shared/test.tf
.The text was updated successfully, but these errors were encountered: