v0.13 - no warnings or fails with multi-file yamls about conftest HOT 8 CLOSED

I have a PR out there that should resolve this.

from conftest.

I looked into this some, and it looks like we broke multi-file yamls. In the provided example, if you remove all but the Deployment config, you'll get some results.

Since the yaml library doesn't support multi-document yaml files, we were detecting line breaks/getting the result of each yaml in the test.go file.

It looks like it was moved to the yaml parser itself.

At first glance, it doesn't look like the Rego evaluation isn't too happy with []interface{}.

from conftest.

Could you include the policy files and input file you're using?

from conftest.

Here goes:

files.zip

# expand folder
$ conftest test external-dns.yaml

from conftest.

Nice find. We’re using kustomize, so most of our configs are multi-document.

from conftest.

Yeah.. definitely a regression. They were working previously. Doing some debugging, we're now passing in []interface{} to the Rego library's Eval() function, and it doesn't seem to be handling it properly.

from conftest.

Ahh, didn;t realize this was a regression. I ran into this yesterday when feeding the output of kustomize build into conftest test. I even worked on "supporting it" (my WIP here).

from conftest.

Well, it's a regression in the sense that multi-file yamls used to work. 0.13 appears to have broken that functionality.

from conftest.