Retrieve specific parameters overrides from PlatformConfig

[antoinebhs]

Requires next powsybl upgrade

Please check if the PR fulfills these requirements

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

Does this PR already have an issue describing the problem?
powsybl/powsybl-core#3066

One build is failing

[antoinebhs]

@SylvestreSakti, this requires the next powsybl upgrade

[SylvestreSakti]

@SylvestreSakti, this requires the next powsybl upgrade

Yes, ok, now I understand that the checks will work with the next release of core.

[jeandemanged]

Looking at powsybl/powsybl-core#3066 we should probably apply the change as well to:

• open-security-analysis-default-parameters
• open-sensitivityanalysis-default-parameters

right ?

[olperr1]

Looking at powsybl/powsybl-core#3066 we should probably apply the change as well to:

* `open-security-analysis-default-parameters`

* `open-sensitivityanalysis-default-parameters`

right ?

@jeandemanged: You are right... but these providers were forgotten in powsybl/powsybl-core#3133.

[olperr1]

After a double-check: SecurityAnalysisProvider and SensitivityAnalysisProvider of powsybl-core don't have a getSpecificParameter() method. This explains why getSpecificParameters(PlatformConfig platformConfigConfig) was not introduced in these interfaces and why no changes were made here for:

• open-security-analysis-default-parameters
• open-sensitivityanalysis-default-parameters

I will open an issue in powsybl-core on this subject, but for now these providers shouldn't be updated.

[olperr1]

I will open an issue in powsybl-core on this subject, but for now these providers shouldn't be updated.

The issue is here: powsybl/powsybl-core#3175

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

See #1093 (comment)