Replies: 1 comment
-
|
Here is the PR with the example terraform and the fix: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Trivy has a bug in it when processing for_each with a map and the locals are unresolvable, here is a proof of concept terraform:
This ends up generating 4 resources for the policy attachment when we only have two
platform_roles. This is because its making a resource for every key on the Pseudo object so there is a resource forid,arn,name, etc. instead of for the role strings.Desired Behavior
I expect to only see two resources for the policy attachment. One for
ecs-tasksand one forlambda.Actual Behavior
Currently I see for resources, one for each key
id,arn,name,assume_policy_arn.Reproduction Steps
I'm following up with a PR that will have a test reproduction.Target
Filesystem
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
MacOS
Version
and
Beta Was this translation helpful? Give feedback.
All reactions