Closed purajit closed 5 days ago
Thanks for this!
For context, the config file originally just pulled in the config file itself. But this is probably the easiest way to pull the custom tests in for execution.
Using plain semver strings makes sense to me, IDK why I did it like this originally.
I was going to ask you to add a custom check to the integration test. But it looks like it's not possible to change the ignored paths for the test runner. So, assuming you've tested this manually, nevermind.
Yeah, I was debating whether to explicitly just add .tfsec/_tfchecks.{yaml,json}
instead of using a glob, but I figured a glob would be better so that we don't have to constantly keep this up-to-date with any additional configs/name changes tfsec might do. And yes, tested manually!
I tested manually myself, looks good! I've got an idea for modifying the rule runner to allow setting the ignore paths. I'm going to merge this and then see if I can get that to work and get a test in.
Test added in https://github.com/pantsbuild/pants/pull/21116 . Turns out it was easier than I thought; bootstrap_args
already does all the plumbing necessary.
@lilatomic @purajit
Is this a breaking change for people who specified the tool version in their pants.toml
?
Yes it is. It's called it out in the release notes, is there somewhere else we should add it?
No, that's the place - but I thought we had a 3-version deprecation rule.
ah, I thought that didn't apply to experimental. It'll be easy to just strip the leading "v" and keep backwards compat, lemme do that
Moved the conversation here: https://pantsbuild.slack.com/archives/C0D7TNJHL/p1719780913456259
check_existence
check search for all configs. Currently, it completely ignores_tfchecks.{yaml,json}
, the standard way to define custom checks.