-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove upward traversal logic for config discovery #479
Remove upward traversal logic for config discovery #479
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One documentation cleanup/clarification point only. Can't argue with the logic, yay!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, for what it's worth. Thanks for making these changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, but a little more wordsmithing....
Co-authored-by: Scott Bailey <72747501+rbailey-godaddy@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw a missing space you can add and then I'm good to go!
files on the command line. Each file is located and processed in order. When | ||
conflicting directives are provided in different files, the value in the last | ||
files on the command line. Paths specified using --config are interpreted | ||
relative to the current working directory.Each file is located and processed in order. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
relative to the current working directory.Each file is located and processed in order. | |
relative to the current working directory. Each file is located and processed in order. |
To help us get this pull request reviewed and merged quickly, please be sure to include the following items:
This PR removes the upward traversal logic for configuration discovery in Tartufo. Tartufo will no longer look for configuration files in unspecified parent directories.
PR Type
What kind of change does this PR introduce?
Backward Compatibility
Is this change backward compatible with the most recently released version? Does it introduce changes which might change the user experience in any way? Does it alter the API in any way?
This is a breaking change for users who were relying on upward traversal for configuration discovery
Issue Linking
Fixes #475