🎨 wb-auth: Configure tracing and network configs

[pcrespov]

What do these changes do?

• 🎨 adds default network to wb-auth
• 🎨 adds tracing config to wb-auth
• 🐛 Fixes tracing config in all services
  • 🔨 add anchor helper for tracing configs

Here a diff of the output of the former (left) and new (right) compose

Related issue/s

• resolves wb-auth: Configure tracing and network configs #8147

How to test

rm .env
make .stack-simcore-production.yml
mv .stack-simcore-production.yml .stack-simcore-production-after.yml
git checkout master
rm .env
make .stack-simcore-production.yml
mv .stack-simcore-production.yml .stack-simcore-production-before.yml
diff .stack-simcore-production-after.yml .stack-simcore-production-before.yml 

Dev-ops

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.08%. Comparing base (c4d6cb2) to head (eef7b5f).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8148      +/-   ##
==========================================
+ Coverage   87.52%   88.08%   +0.55%     
==========================================
  Files        1891     1891              
  Lines       72835    72836       +1     
  Branches     1279     1279              
==========================================
+ Hits        63749    64154     +405     
+ Misses       8707     8302     -405     
- Partials      379      380       +1     

Flag	Coverage Δ
integrationtests	64.23% <0.00%> (+3.83%)	⬆️
unittests	86.69% <100.00%> (-0.02%)	⬇️

Components	Coverage Δ
pkg_aws_library	93.93% <ø> (ø)
pkg_celery_library	87.34% <ø> (ø)
pkg_dask_task_models_library	79.62% <ø> (ø)
pkg_models_library	93.11% <ø> (ø)
pkg_notifications_library	85.26% <ø> (ø)
pkg_postgres_database	88.02% <ø> (ø)
pkg_service_integration	70.19% <ø> (ø)
pkg_service_library	71.48% <ø> (-0.05%)	⬇️
pkg_settings_library	90.45% <ø> (ø)
pkg_simcore_sdk	85.05% <ø> (ø)
agent	93.81% <ø> (ø)
api_server	93.02% <ø> (ø)
autoscaling	95.88% <ø> (ø)
catalog	92.34% <ø> (ø)
clusters_keeper	99.13% <ø> (ø)
dask_sidecar	92.37% <ø> (ø)
datcore_adapter	97.94% <ø> (ø)
director	76.14% <ø> (ø)
director_v2	91.08% <ø> (+5.62%)	⬆️
dynamic_scheduler	96.27% <ø> (ø)
dynamic_sidecar	90.07% <ø> (ø)
efs_guardian	89.76% <ø> (ø)
invitations	91.44% <ø> (ø)
payments	92.60% <ø> (ø)
resource_usage_tracker	92.39% <ø> (-0.11%)	⬇️
storage	86.39% <ø> (-0.34%)	⬇️
webclient	∅ <ø> (∅)
webserver	88.15% <100.00%> (+0.02%)	⬆️

---

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 c4d6cb2...eef7b5f. 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.

[mrnicegyu11]

very nice, thanks!

[pcrespov]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The following conditions don't match anymore:

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-neutral = unit-tests
      • check-skipped = unit-tests
      • check-success = unit-tests

[matusdrobuliak66]

👍

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[sanderegg]

thanks. we still need to ensure this is disabled for all tests.

[pcrespov]

@mergify queue

[pcrespov]

@Mergifyio requeue

[mergify]

queue

🟠 Waiting for conditions to match

• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
    • #approved-reviews-by>=2
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • #review-threads-unresolved=0
    • -conflict
    • -draft
    • base=master
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • label!=🤖-do-not-merge
    • label=🤖-automerge
    • any of: [🛡 GitHub branch protection]
      • check-skipped = deploy to dockerhub
      • check-neutral = deploy to dockerhub
      • check-success = deploy to dockerhub
    • any of: [🛡 GitHub branch protection]
      • check-success = system-tests
      • check-neutral = system-tests
      • check-skipped = system-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = unit-tests
      • check-neutral = unit-tests
      • check-skipped = unit-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = check OAS' are up to date
      • check-neutral = check OAS' are up to date
      • check-skipped = check OAS' are up to date
    • any of: [🛡 GitHub branch protection]
      • check-success = integration-tests
      • check-neutral = integration-tests
      • check-skipped = integration-tests
    • any of: [🛡 GitHub branch protection]
      • check-success = build-test-images (frontend) / build-test-images
      • check-neutral = build-test-images (frontend) / build-test-images
      • check-skipped = build-test-images (frontend) / build-test-images

[mergify]

requeue

☑️ This pull request is already queued

[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