PLAT-3196: read trending weights from the Paradigm platform

Rees Morrisrequested to merge
PLAT-3196 into master

This MR makes the popularity task read each journal's and press's trending weights from the Paradigm API gateway (GET /api/v1/site/{code}/popular-articles or /trending-books, src/platform_settings.py) with metrics-api's own internal key, instead of Consul's trending_content, which the CMS now owns (PLAT-3196, Central Station checklist C8). When the platform can't be read or answers anything but 200, calculate_service_popularity_metrics logs and keeps the last ranking, where a Consul failure used to re-rank every Service with the default weights; a missing PARADIGM_API_URL or PARADIGM_API_KEY is logged at error level.

  • Ship order: the kubernetes chart MR (Secret and PARADIGM_API_URL on the workers) merges first, and a metrics-api release without this change deploys with the env and is checked in a worker pod; only then tag this one (see the chart's README).
  • up-consul and src/consul.py go.

🤖 Generated with Claude Code

Merge request reports