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
Hi @ferrarimarco, appreciate the bug report. I verified the issue on my dev box, and it's definitely a policy bug.
Basically, it looks like the intention for the checkIpForward rule was to check if !(.can_ip_forward == true), but due to syntax, "not api.config.can_ip_forward" actually checks if a key does not exist, which in this case is true (it's not in the test file).
Since the can_ip_forward rule defaults to false, removing the "not" and just checking for can_ip_forward == true should suffice.
Description
Terrascan reports a violation of the accurics.gcp.NS.130 rule (rule code is in checkIpForward.rego), and it should not.
What I Did
Here's my
google_compute_instance
. Adding acan_ip_forward = false
doesn't make any difference.What am I doing wrong?
The text was updated successfully, but these errors were encountered: