✨ Is353/api results table from meta-project sweep (⚠️ devops)

[pcrespov]

What do these changes do?

This PR adds new entrypoints in the API to retrieve the iterations results. An iteration result basically contains the values produced (e.g. iterator) and observed (probes) in the iteration working copy project.

The webserver API introduces a new entry to list all results of a meta-project. Returns a table-like json with information about valuds produced and observer. This is the third entry in this view:

Next PRs

• Access to some of the meta entrypoints above via api-server e.g. to create/retrieve results from different projects
• Run functional nodes in computational backend

Extras

• Re-enables access to /dev/docs (both reverse proxy and web-server settings) by default. SEE additions in trafik rules in services/docker-compose.yml (⚠️ devops)

Related issue/s

• S-D22.2 Meta-Modeling sensitivity analysis Y4M08 osparc-issues#353
• S-D22.3 Meta-Modeling uncertainty assessment Y4M10 osparc-issues#354
• ⚗️ MetaModeling backlog #2392

How to test

cd osparc-simcore
make devenv
source .venv/bin/activate
cd services/web/server 
make install-dev
pytest --pdb -vv tests/**/meta_mode*.py

Checklist

• test results in workflow test
• add access in server-api (separated PR?)
• Openapi changes? make openapi-specs, git commit ... and then make version-*)
• Database migration script? cd packages/postgres-database, make setup-commit, sc-pg review -m "my changes"
• Unit tests for the changes exist
• Runs in the swarm
• Documentation reflects the changes
• New module? Add your github username to .github/CODEOWNERS

[codecov]

Codecov Report

Merging #2851 (2f5278d) into master (0df1384) will increase coverage by 16.4%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #2851      +/-   ##
=========================================
+ Coverage    72.8%   89.2%   +16.4%     
=========================================
  Files         672      26     -646     
  Lines       27482     531   -26951     
  Branches     3206      48    -3158     
=========================================
- Hits        20008     474   -19534     
+ Misses       6824      46    -6778     
+ Partials      650      11     -639     

Flag	Coverage Δ
unittests	89.2% <ø> (+16.5%)	⬆️

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

Impacted Files	Coverage Δ
...imcore_service_webserver/meta_modeling_handlers.py
...core_service_webserver/meta_modeling_iterations.py
...service_webserver/meta_modeling_version_control.py
...sdk/src/simcore_sdk/node_ports_common/dbmanager.py
...rector_v2/modules/comp_scheduler/dask_scheduler.py
...base/src/simcore_postgres_database/models/users.py
...core_service_api_server/api/routes/solvers_jobs.py
.../director/src/simcore_service_director/producer.py
...re_service_director_v2/models/schemas/constants.py
...imcore_service_webserver/exporter/async_hashing.py
... and 636 more

[GitHK]

Looking nice.
Due to lack of familiarity with this feature, I have some questions below.

[KZzizzle]

good to know, thanks!

[odeimaiz]

👌

[sanderegg]

ok so I had a quick look in the deploy repository and this will open the dev/doc to anyone. let's discuss if that is the wanted behaviour

[pcrespov]

@sanderegg so at the end PathPrefix(/v0/, /dev/) was added in docker-compose.local.yml (i.e. for local development) so it should NOT collide with compose-spec file added in operations.