[K9VULN-12170] Ignore empty configuration files#865
Merged
jasonforal merged 1 commit intomainfrom Mar 27, 2026
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates CLI configuration loading to treat empty (or whitespace-only) YAML config files as “not present”, preventing schema validation failures when users intentionally leave config blank.
Changes:
- Skip parsing Code Security (
v1) and legacy config files when file contents are empty/whitespace-only. - Remove the explicit error previously raised for an empty legacy config file.
- Add a unit test ensuring empty config files are ignored.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
a3e1287 to
4eb5651
Compare
jdelgo
approved these changes
Mar 27, 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
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.
What problem are you trying to solve?
Static analysis currently fails if an empty configuration file is encountered. While technically invalid (i.e. doesn't pass schema validation), an empty file should be ignored, as the intent is clearly to not have any configuration.
What is your solution?
Only attempt to parse the file as a configuration if it isn't empty.
Alternatives considered
What the reviewer should know