how to suppress these error reported by Terrascan

[ravitomardevops]

• terrascan version: v14
• Operating System: Ubuntu (Github Action)

Description

trying to run terrascan on my modules
Showing false scanning errors :

IaC Type            :	terraform
Directory           :	/path/to/module/modules
Error Message       :	directory '/path/to/module/modules' has no terraform config files

-----------------------------------------------------------------------

IaC Type            :	terraform
Directory           :	/home/runner/work/path/to/module/modules/compute
Error Message       :	directory '/home/runner/path/to/module/modules/compute' has no terraform config files

What I Did

I ran simple terrsacan

Paste the command(s) you ran and the output.
terrascan scan  -d . -i terraform --iac-version v14 -t all --log-output-dir $(pwd)

-----------------------------------------------------------------------
	
	IaC Type            :	terraform
	Directory           :	/path/to/module/modules
	Error Message       :	directory '/path/to/module/modules' has no terraform config files
	
	-----------------------------------------------------------------------
	
	IaC Type            :	terraform
	Directory           :	/home/runner/work/path/to/module/modules/compute
	Error Message       :	directory '/home/runner/path/to/module/modules/compute' has no terraform config files

[ravitomardevops]

@Rchanger please help how i can supress these warning

[Rchanger]

@ravitomardevops we added these logs since we were receiving multiple bugs stating we don't see any error but the exit code is non-zero. We will start a discussion about these to make it controlled via flag. I'll update you on this once we decide something. Thank you

[shadycuz]

@Rchanger It would be really nice to have an option to not fail the scan just because it found an empty directory.

I want to use terrascan to scan a terraform module but it fails because examples/ and modules/ don't have any terraform in them even though they have subdirectories that do.

Maybe the title of this issue could be updated?

[lexyiouroukis]

flagging --non-recursive resolves this problem for me.