John Reese

I added #536 to hopefully clarify the behavior. Looks like the docs on the website showcase the current behavior: https://www.conftest.dev/options/#-data At the moment the folder itself doesn't come into play,...

To represent what you're trying to do in Conftest, it would be: `conftest test a/dir/data.json -p a` Typically you'll pass in the configuration that you're trying to test (data.json) and...

Yeah I see, the `--data` for Conftest will take the data files passed in and make them accessible based on their keys. So in this case, `{"v":1}` would be accessible...

@anderseknert are you familiar with OPA and using bundles? There does appear to be a difference with how Conftest and OPA handle external data, but I'm not familiar with them...

Thanks! The documentation has been updated to reflect reality. I'll play around with --data and --bundle and see if it makes sense to change. The fear being that I imagine...

> Yeah, I guess a sensible middle ground could be to keep current behavoir while introducing the `--bundle` flag for conftest too, and have that act exactly as it does...

@mykter @anderseknert I just noticed that OPA also has a `--data` flag. Using the above example, if you use OPA's `--data` flag the example is the same as Conftest. i.e....

Some thoughts from Slack: - "Exception" verbiage in its current form could be considered confusing. A better name may be "Exclusions" to represent what is really happening. Also "Skip" or...

I definitely agree that when the configurations can't even be evaluated due to `rego` that doesn't compile, missing files, etc the `--fail-on-warn` flag needs to return `2`. It currently returns...

I cheated a little bit and looked at the implementation 🦝 and have a couple thoughts: #### Using the library In a _perfect_ world, you'd be able to use the...