-
Notifications
You must be signed in to change notification settings - Fork 6
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
Allow specification of custom default file for finding-cfgs #373
Conversation
3f940a3
to
746377a
Compare
746377a
to
3282542
Compare
3282542
to
0162bcb
Compare
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.
having an abstraction between configuration (findings-cfgs) and their respective sources seems like a good idea.
However, can we split the cfg for data-sources, from the "retriever"? More concretely-speaking, I would suggest to drop the retrieve
-methods, and instead define a function (maybe following our lookup-pattern: a "findings-cfg-lookup" that will accept cfg-references and return resolved objects) or class.
0162bcb
to
40f70d3
Compare
40f70d3
to
e6306ed
Compare
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: