Repository navigation
feat(autodetect): apply plugin-declared project exclusions [FIX-592] - #29
Merged
Merged
Conversation
Plugins declare when another format supersedes them (exclude_if_repo_contains, exclude_if_inside) and autodetect applies those instead of hardcoding the rules per format. Only projects that survive filtering can exclude anything, so a directory dropped for having no provider or backend no longer silently discards its whole subtree - which is what dropped ~2.9k projects in one repo. The pre-plugin rules are kept for the path that runs without any plugins, where identification also falls back to local file sniffing.
owenrumney
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Autodetect now applies the exclusion conditions plugins declare (proto v1.167.0) instead of hardcoding per-format rules. Fixes FIX-592, where ~2.9k projects in one repo silently disappeared.
exclude_if_repo_containsreplaces "if terragrunt exists anywhere, drop all terraform projects"exclude_if_insidereplaces "drop non-terraform/terragrunt projects nested in a project" — that rule was written for CloudFormation but caught every other type, which is what dropped the projects.tfwith no provider or backend) no longer suppresses its subtree — previously it did so while not even appearing in the outputgenerate_test.goexpectations are unchanged.Needs the plugin releases already out: terraform v0.0.53, cloudformation v0.0.34, terragrunt v0.0.55.
Testing
Full suite green,
golangci-lintclean. Four new e2e tests against the released plugins; the two FIX-592 ones were confirmed to fail before this change (0 cisco projects, CFN template suppressed).