-
Notifications
You must be signed in to change notification settings - Fork 51
Add itools parameters for Security analysis #3722
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
Open
samirromdhani
wants to merge
8
commits into
main
Choose a base branch
from
feat/security_analysis_itools_with_json_inputs_parameters
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add itools parameters for Security analysis #3722
samirromdhani
wants to merge
8
commits into
main
from
feat/security_analysis_itools_with_json_inputs_parameters
Conversation
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
ad523d0 to
f6d6229
Compare
bf2f32c to
eb687da
Compare
…es from a JSON Signed-off-by: Samir Romdhani <[email protected]>
…s file options Signed-off-by: Samir Romdhani <[email protected]>
Signed-off-by: Samir Romdhani <[email protected]>
…ents under itools security analysis Signed-off-by: Samir Romdhani <[email protected]>
Signed-off-by: Samir Romdhani <[email protected]>
Signed-off-by: Samir Romdhani <[email protected]>
07a6679 to
84f53ff
Compare
Signed-off-by: Samir Romdhani <[email protected]>
cf3d719 to
aa386df
Compare
Signed-off-by: Samir Romdhani <[email protected]>
|
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.



Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Fixes #3708
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information:
A new contingencies provider was added to parse contingencies from JSON files:
JsonContingenciesProviderFactoryconfig.yml :
Adding 2 examples in the doc (example 3 and 4)