refactor: remove PYMS microservice, use ZarinPal directly in CMS
Build and Deploy to Kubernetes / build-and-deploy (push) Successful in 8m26s

- Remove PYMSPaymentService.cs and PYMS proto files
- Remove 'pyms' case from DI ConfigureServices
- Remove PYMS config from appsettings
- Switch PaymentProvider to 'zarinpal' (direct integration)
- ZarinPalPaymentService handles sandbox/production, verify, errors
- PYMS deployment/service/ingress removed from K8s
This commit is contained in:
masoodafar-web
2026-02-15 23:25:20 +03:30
parent 2502cbbda2
commit 207f53ef80
7 changed files with 3 additions and 621 deletions
@@ -75,7 +75,7 @@ public static class ConfigureServices
}
// Payment Gateway Service - Multi-Provider Architecture
// پشتیبانی از درگاه‌های مختلف: ZarinPal, Daya, PYMS, Mock
// پشتیبانی از درگاه‌های مختلف: ZarinPal, Daya, Mock
var paymentProvider = configuration.GetValue<string>("PaymentProvider", "Mock")?.ToLowerInvariant();
switch (paymentProvider)
@@ -90,11 +90,6 @@ public static class ConfigureServices
.SetHandlerLifetime(TimeSpan.FromMinutes(5));
break;
case "pyms":
// PYMS (Payment Microservice) — ارتباط gRPC با سرویس پرداخت مستقل
services.AddSingleton<IPaymentGatewayService, PYMSPaymentService>();
break;
case "mock":
default:
services.AddScoped<IPaymentGatewayService, MockPaymentGatewayService>();