Skip to content
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

Refactoring security-analysis-api : SecurityAnalysisImpl (issue 1604) #1648

Merged

Conversation

tadam50
Copy link
Contributor

@tadam50 tadam50 commented Mar 4, 2021

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX' and skip the rest
#1604

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the current behavior? (You can also link to an open issue here)
security-analysis-api has an default implementation of SecurityAnalysisProvider

What is the new behavior (if this is a feature change)?
A new aggregate module is created : security-analysis
This new module contains previous security-analysis-api and the new one security-analysis-default
security-analysis-default module contains the default implementation of SecurityAnalysisProvider based on LoadFlow

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:

  • The Breaking Change or Deprecated label has been added
  • The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

All interceptors tests have been move into new module security-analysis-default

tadam50 added 2 commits March 3, 2021 09:33
Signed-off-by: Thomas ADAM <tadam@silicom.fr>
Signed-off-by: Thomas ADAM <tadam@silicom.fr>
Signed-off-by: Thomas ADAM <tadam@silicom.fr>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 53 Code Smells

83.0% 83.0% Coverage
0.5% 0.5% Duplication

@miovd miovd merged commit 2a41aaa into integration/refactoring-security-analysis-api Mar 22, 2021
@miovd miovd deleted the as_refactoring_issue_1604 branch March 22, 2021 13:20
miovd pushed a commit that referenced this pull request May 4, 2021
miovd pushed a commit that referenced this pull request May 4, 2021
miovd pushed a commit that referenced this pull request May 25, 2021
EtienneLt pushed a commit that referenced this pull request May 27, 2021
miovd pushed a commit that referenced this pull request Jun 14, 2021
miovd added a commit that referenced this pull request Jun 14, 2021
* Remove deprecated code (#1579)
* Use ServiceLoader to create SecurityAnalysis (#1585)
* Add SecurityAnalysisProvider
* Add FIXME to rename later and fix comments issues
* Remove runWithLog method in SecurityAnalysisProvider
* Replace SecurityAnalysis factory uses by loaded SecurityAnalysisProvider (#1618)
* Refactoring security-analysis-api : SecurityAnalysisImpl (issue 1604) (#1648)
* Refactoring security-analysis-api : Remove WithLog suffixed methods (#1667)
* Remove SecurityAnalysisResultWithLog class
* Replace WithLog methods with bollean usage
* Add SecurityAnalysisReport composed by SecurityAnalysisResult & LogBytes

Signed-off-by: Thomas ADAM <tadam@silicom.fr>

* After rebasing: bump to 4.2.0-SNAPSHOT version + do not use "default" word in automatic module name (forbidden)
* Add default impl of API AS in distribution core
* Bump to 4.3.0-SNAPSHOT

Signed-off-by: RALAMBOTIANA MIORA <miora.ralambotiana@rte-france.com>

* Monitor security analysis (#1737)
* On demand results for specific equipments

Signed-off-by: Etienne Lesot <etienne.lesot@rte-france.com>

* Corrections following reviewer's comments:
- Rename SecurityAnalysisResult.getPreContingencyLimitViolationsResult
- Use only pre/post contingency in javadoc
- Put methods in StateMonitorJson in StateMonitor
- Clear before addAll in setMonitors
* Corrections following reviewer's comments:
- PreContingencyResult constructor requires Collections, not Maps
- Correct SecurityAnalysisResult deserializer and test files
- Optimize monitor merging in StateMonitorIndex
- Add ID-based getters in PreContingencyResult
- Delete redundant methods in SecurityAnalysisResult
- If a monitored ID does not exist, ignore it
- Add tests
* Rebasing from master and resolving conflicts


Co-authored-by: RALAMBOTIANA MIORA <miora.ralambotiana@rte-france.com>
Co-authored-by: EtienneLt <32468651+EtienneLt@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants