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
As you can see, I've added extra comands above (pwd, ls) to make sure I'm in the correct working dir. And I also executed the terrascan scan command against various interpretations of the same destination path. All showing the same result: 0 policies validated.
The text was updated successfully, but these errors were encountered:
I have a quick question:
How is the volume being attached to the terrascan container at ./terraform directory? I cannot see a section in .gitlab-ci.yaml shared above. Just want to make sure the code is being added into the terrascan container, just the way it is being attached with -v option when you are running it locally.
Thanks to your input I found out that I wrongly mounted the folder in the docker run command. I've fixed this and updated the intial report. This doesn't explain the difference though.
I assume the reason why there were 0 rules processed is because OCI cloud provider isn't supported and hence no rules could be applied. Therefore I'm closing this issue.
Description
Terrascan doesn't process any rules when running via Gitlab's CI. Local processing against the same repo works well.
What I Did
Running locally works fine (my terraform files are in the
./terraform
directory):However from the Gitlab's CI I get:
My
.gitlab-ci.yaml
configuration follows:As you can see, I've added extra comands above (
pwd
,ls
) to make sure I'm in the correct working dir. And I also executed theterrascan scan
command against various interpretations of the same destination path. All showing the same result: 0 policies validated.The text was updated successfully, but these errors were encountered: