🎨 web-api services api response includes manifest info (part 5)

[pcrespov]

What do these changes do?

Connects manifest to services web-api response (requirement for UI)

The service metadata returned by the API is composed of two intersecting parts, namely a "published" and an "editable" parts. The first comes from the manifest (i.e. metadata from services in the docker registry and function-services) and the second comes from the services_meta_data table.

This PR completes the service meta-data returned in the API by accessing and merging the "published" part. This part includes fields like inputs/outputs, etc

Extras

• 🔨 prints actual docker-compose specs used in the tests

Related issue/s

• Part of Front-end uses new catalog/services/* web API entrypoint #5964

How to test

• Main driving test services/catalog/tests/unit/with_dbs/test_services_services_api.py
• Manual testing /dev/catalog/services/* entrypoints using swagger site
  • set WEBSERVER_DEV_FEATURES_ENABLED=1 in .env
  • deploy
  • Execute entrypoint and should receive a complete answer
    

Following PR will address:

• evaluate and add compatibility field in response body

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 88.0%. Comparing base (cafbf96) to head (0c36058).
Report is 350 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6061      +/-   ##
=========================================
+ Coverage    84.5%   88.0%    +3.5%     
=========================================
  Files          10    1438    +1428     
  Lines         214   59148   +58934     
  Branches       25    1409    +1384     
=========================================
+ Hits          181   52106   +51925     
- Misses         23    6746    +6723     
- Partials       10     296     +286     

Flag	Coverage Δ
integrationtests	64.8% <ø> (?)
unittests	86.1% <100.0%> (+1.5%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...mcore_service_catalog/api/dependencies/services.py	88.0% <ø> (ø)
...g/src/simcore_service_catalog/api/rpc/_services.py	100.0% <100.0%> (ø)
...imcore_service_catalog/db/repositories/services.py	81.3% <100.0%> (ø)
...g/src/simcore_service_catalog/services/director.py	91.9% <ø> (ø)
...g/src/simcore_service_catalog/services/manifest.py	86.1% <100.0%> (ø)
...c/simcore_service_catalog/services/services_api.py	77.9% <100.0%> (ø)

... and 1394 files with indirect coverage changes

[odeimaiz]

👍

[bisgaard-itis]

Very cool. Just a question for my understanding. Thanks