✨ web-api interface for tags sharing and add to services

[pcrespov]

What do these changes do?

Creates the web-api (w/o implementation) to both share tags and assign tags to services.

• ✨ Extended web-api (0.42.0 → 0.43.0) to share tags and add(rm) tags to services
• 📝 Cleaned up openapi specs tags to document better sharing (associations with group) and sub-resource associations (e.g. tags in services or projects)

web-api

• Open Swagger Editor
• share tags with other groups
  
• add/remove (existing) tags to (existing) projects and now also to (existing) catalog's services. Note that this adds or removes a relation/association since neither of the resources are created or deleted here.
  

Related issue/s

• Part of Can use tags in services and list services grouped by tags #6202

How to test

cd services/web/server
make install-dev
pytest -vv tests/unit/with_dbs -k test_app_named_resources_against_openapi_specs

Dev-ops checklist

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

[codecov]

Codecov Report

Attention: Patch coverage is 79.38931% with 27 lines in your changes missing coverage. Please review.

Project coverage is 82.3%. Comparing base (cafbf96) to head (2759e90).
Report is 514 commits behind head on master.

Files with missing lines	Patch %	Lines
...er/src/simcore_service_webserver/tags/_handlers.py	59.0%	18 Missing ⚠️
...imcore_service_webserver/catalog/_tags_handlers.py	72.7%	9 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6298      +/-   ##
=========================================
- Coverage    84.5%   82.3%    -2.2%     
=========================================
  Files          10     591     +581     
  Lines         214   30176   +29962     
  Branches       25     260     +235     
=========================================
+ Hits          181   24861   +24680     
- Misses         23    5255    +5232     
- Partials       10      60      +50     

Flag	Coverage Δ
integrationtests	64.6% <74.8%> (?)
unittests	87.9% <79.3%> (+3.3%)	⬆️

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

Files with missing lines	Coverage Δ
...er/src/simcore_service_webserver/catalog/plugin.py	100.0% <100.0%> (ø)
...mcore_service_webserver/projects/_tags_handlers.py	93.3% <100.0%> (ø)
...rver/src/simcore_service_webserver/tags/schemas.py	100.0% <100.0%> (ø)
...imcore_service_webserver/catalog/_tags_handlers.py	72.7% <72.7%> (ø)
...er/src/simcore_service_webserver/tags/_handlers.py	83.1% <59.0%> (ø)

... and 596 files with indirect coverage changes

[matusdrobuliak66]

Thanks! As discussed, for future consideration (and also for future resources): since a tag is a resource that is bound either to a service or a project, I believe we do not need to have a tag-sharing functionality. Additionally, we do not need to bother the user with sharing tags.

A valid approach might be to resolve permissions in the service layer of the tag as the first step. If it's a project tag, check whether the user has write permissions for the project. If it's a service tag, check whether the user has write permissions for the service. If the user does not have the necessary permissions, we do not allow to proceed further.

[sanderegg]

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 SonarCloud