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-s3.yaml	issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk	2026-10-24 12:01:25 +05:00
celery-s3.yaml	issues: SAREX_API from env, in-cluster Django in uralkal, vad, ugmk	2026-10-24 12:01:25 +05:00
kafka-app.yaml	**Update d8-ugmk-prod configurations to fix service references and ensure proper workflow and API integration**	2026-10-20 18:01:28 +03:00
kafka-ca-configmap.yaml	++	2026-08-09 14:52:30 +05:00
kustomization.yaml	**Update d8-ugmk-prod configuration: replace SAREX_API and related endpoints with sarex.uralmine.com and adjust production ConfigMap.**	2026-10-20 17:42:13 +03:00
namespace.yaml	++	2026-07-31 12:55:03 +05:00
production-configmap.yaml	**Update d8-ugmk-prod configurations to fix service references and ensure proper workflow and API integration**	2026-10-20 18:01:28 +03:00