🐛 Fixes contract limit parameter

[matusdrobuliak66]

What do these changes do?

• 🐛 Fixes contract limit parameter after 🎨Storage: Increased maximum number of returned paths to 1000 #7305

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.69%. Comparing base (9f5b9a1) to head (52e9b3e).
Report is 1 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (9f5b9a1) and HEAD (52e9b3e). Click for more details.

HEAD has 28 uploads less than BASE

Flag	BASE (9f5b9a1)	HEAD (52e9b3e)
unittests	29	1

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #7309       +/-   ##
===========================================
- Coverage   85.69%   69.69%   -16.01%     
===========================================
  Files        1692      744      -948     
  Lines       65759    34523    -31236     
  Branches     1121      168      -953     
===========================================
- Hits        56355    24061    -32294     
- Misses       9084    10404     +1320     
+ Partials      320       58      -262     

Flag	Coverage Δ		*Carryforward flag
integrationtests	65.42% <ø> (+0.02%)	⬆️	Carriedforward from a4a3bc3
unittests	90.68% <ø> (+6.04%)	⬆️

*This pull request uses carry forward flags. Click here to find out more.

Components	Coverage Δ
api	∅ <ø> (∅)
pkg_aws_library	∅ <ø> (∅)
pkg_dask_task_models_library	∅ <ø> (∅)
pkg_models_library	∅ <ø> (∅)
pkg_notifications_library	∅ <ø> (∅)
pkg_postgres_database	∅ <ø> (∅)
pkg_service_integration	∅ <ø> (∅)
pkg_service_library	∅ <ø> (∅)
pkg_settings_library	∅ <ø> (∅)
pkg_simcore_sdk	77.30% <ø> (-8.16%)	⬇️
agent	∅ <ø> (∅)
api_server	90.68% <ø> (ø)
autoscaling	∅ <ø> (∅)
catalog	∅ <ø> (∅)
clusters_keeper	∅ <ø> (∅)
dask_sidecar	∅ <ø> (∅)
datcore_adapter	∅ <ø> (∅)
director	∅ <ø> (∅)
director_v2	78.60% <ø> (-12.70%)	⬇️
dynamic_scheduler	∅ <ø> (∅)
dynamic_sidecar	89.43% <ø> (-0.86%)	⬇️
efs_guardian	∅ <ø> (∅)
invitations	∅ <ø> (∅)
osparc_gateway_server	∅ <ø> (∅)
payments	∅ <ø> (∅)
resource_usage_tracker	∅ <ø> (∅)
storage	∅ <ø> (∅)
webclient	∅ <ø> (∅)
webserver	59.41% <ø> (-20.91%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f5b9a1...52e9b3e. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sanderegg]

how do you generate these contracts? are there calls to be done?
could that be setup via make openapi-specs ?

And for the record, that limit was wrongly setup before my PR, e.g. the OpenAPI was advertising the wrong numbers.

[matusdrobuliak66]

how do you generate these contracts? are there calls to be done? could that be setup via make openapi-specs ?

And for the record, that limit was wrongly setup before my PR, e.g. the OpenAPI was advertising the wrong numbers.

@sanderegg This is still a work in progress, but these contracts are generated by code on the consumer side (in this case, Sim4Life). Their purpose is to remain unchanged. Of course, in this special situation, you need to talk to the specific consumer, which in this case is Sim4Life.

Meanwhile, I also store them as a reference in our codebase. The publishing process is explained in the README file. A special tool called pact-broker is used for that.

[bisgaard-itis]

Thanks

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud