ivan c36406209f issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk ... The base production.py hardcoded SAREX_API = https://srx.wb.ru, ignoring the env, so issue export (GET /api/core/users/<id>/) failed from closed contours with CERTIFICATE_VERIFY_FAILED. Read it from SAREX_API with the old value as default; wb keeps it. uralkal, vad, d8-ugmk-prod: SAREX_API -> backend-svc.django:80 (server-side calls, no TLS), and SAREX_HOST set to the contour's public host so links in exports and notifications stay external.		2026-10-24 12:01:25 +05:00
..
backend.yaml	++	2026-08-13 20:14:25 +05:00
celery.yaml	++	2026-08-13 20:14:25 +05:00
frontend.yaml	++	2026-08-13 20:14:25 +05:00
kustomization.yaml	++	2026-08-03 14:32:07 +05:00
namespace.yaml	++	2026-04-21 15:49:58 +05:00
production-configmap.yaml	issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk	2026-10-24 12:01:25 +05:00
redis-deployment.yaml	++	2026-08-03 14:32:07 +05:00
redis-service.yaml	++	2026-08-03 14:32:07 +05:00