-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
glob(i.e. **) does not work in target match for policies #142
Comments
@briantkennedy Any idea why this isn't working? |
More generally, it looks like wildcards inside the path are not working at all. For example, |
I'll take a look, this may be due to some of the work I did for constraint backward compatibility. |
I looked into this and I'm not sure why this isn't quite working. I've created a PR that adds unit tests for these specific cases and it appears to be working as intended. @xingao267 can you provide the version of config validator you're using, a link to template and constraint that is giving the error and a copy of resources that are problematic? |
@briantkennedy thanks for looking into this. I'm using Forseti deployed by Forseti Terraform module version 5.2.1, which is using Forseti version 2.25.1. I don't know what CV version is used by Forseti 2.25.1. Error occurs whenever I use a constraint like the one pasted in this issue. It also gives error like the following:
I can give you access to our forseti instance. Ping me if you need it. |
Now that I'm taking another look at the error message, this is quite strange. I had to go back in the history of the repo to find @gkowalski-google How would we get the FCV version associated with the terraform install to confirm that they are running an older version? |
@briantkennedy Forseti v2.25.1 is using a static binary of CV that was included in the repo; I don't know exactly what version this was but it was some time in October 2019. The main branch has been updated to running CV as a docker container using this tag. |
@briantkennedy @gkowalski-google thanks, let me try with forseti module at master branch. Is there an ETA for the next Forseti release to use newer version of CV? Btw, what's the CV version used in CFT Scorecard? Or I guess it's the latest if it's used as a go library? |
@xingao267 did you have any luck with Forseti main branch? |
@gkowalski-google unfortunately no, I did few trials with the main branch but couldn't make Forseti work, so decided to wait for the next Forseti version released and then try from there. |
When I use ** in the
target
field undermatch
, Forseti Config Validator errors out.Policy:
Error message snippet:
From the CV regex matching tests, it seems such feature is supported.
It's a very useful feature to help make sure policy target can always match the ancestry path no matter what
composite_root_resources
in the forseti server config is.The text was updated successfully, but these errors were encountered: