You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2022. It is now read-only.
As a user of Hawkeye I want to be able to configure modules in an easy way So that I can tackle their full power
Description
Similarly to #115 there are additional cases where we want to be able to configure modules. Another example is the OWASP checker, where we have a use-case of configuring the enableArtifactory configuration.
Rather than creating a second feature request we thought it would make more sense to come up with a feature first that would provide functionality, so that we can create Issues next to add this to the modules.
Acceptance Criteria
Given a module supports configuration values
When passing a new customised configuration
Then the configuration should be passed to the module
And used for the call
Given a module supports configuration values
When passing an existing customised configuration
Then the configuration should be passed to the module
And overrides the existing value to be used for the call
Unresolved Questions
where to put the information? i.e. is the rc file the right place?
how would the configuration look?
how to know if a module supports configuration overwrites, and if, which?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Template
As a user of Hawkeye
I want to be able to configure modules in an easy way
So that I can tackle their full power
Description
Similarly to #115 there are additional cases where we want to be able to configure modules. Another example is the OWASP checker, where we have a use-case of configuring the
enableArtifactory
configuration.Rather than creating a second feature request we thought it would make more sense to come up with a feature first that would provide functionality, so that we can create Issues next to add this to the modules.
Acceptance Criteria
Given a module supports configuration values
When passing a new customised configuration
Then the configuration should be passed to the module
And used for the call
Given a module supports configuration values
When passing an existing customised configuration
Then the configuration should be passed to the module
And overrides the existing value to be used for the call
Unresolved Questions
The text was updated successfully, but these errors were encountered: