master-zapier-plan-draft/packages/verae-fleet/services/customer-service.json
George Lambert 1b199ca4d4
Some checks are pending
offline / test (push) Waiting to run
Separate Zapier, web, API, and leaf access planes with NATS authz
Zapier is one ingress. Direct web, customer API, and S2S leaf nodes are their own services. Every hop to an internal subject must pass verae.access.authz.check (default deny by plane).
2026-09-11 16:05:05 -04:00

28 lines
876 B
JSON

{
"id": "customer-service",
"title": "Customer-service credits and review",
"kind": "http",
"package": "zappier-customer-service",
"role": "customer-service",
"managed": true,
"runtime": "HTTP :3011 CS credits + NATS statement review",
"health": { "type": "http", "path": "/health", "timeoutMs": 2000 },
"ports": { "healthBase": 3011 },
"spawn": {
"cwd": "../zappier-customer-service",
"command": "node",
"args": ["src/server.js"]
},
"env": {
"PORT": "3011",
"ZAPPIER_ADMIN_URL": "http://127.0.0.1:3000",
"ACCOUNT_BALANCE_URL": "http://127.0.0.1:3010",
"NATS_URL": "nats://127.0.0.1:4222",
"AUTHZ_URL": "http://127.0.0.1:3020"
},
"nats": {
"in": [],
"out": ["verae.billing.statement.get", "verae.billing.balance.adjust"]
},
"notes": "CS review and credits. Balances live on account-balance over NATS."
}