Integration Deployment and Operations

---

Epic: Containerization

Plan: Package the gateway as a Docker container with health checks, readiness probes, and environment-based secrets resolution.

Architectural Context: Multi-stage Dockerfile based on node:20-alpine with a non-root user. Health check (/healthz) verifies service liveness; readiness check (/statusz) verifies dependency connectivity. Secrets are resolved from environment variables at startup, with a migration path to Doppler.

Tasks

• Build multi-stage Dockerfile (node:20-alpine, non-root user)
• Implement health check (/healthz) and readiness check (/statusz)
• Configure environment-based secrets resolution at startup

---

Epic: CI/CD Pipeline

Plan: Build a CI/CD pipeline with lint, test, build, and deploy stages. Staging deploys automatically; production requires manual approval.

Architectural Context: The pipeline enforces quality gates at every stage: lint, unit test, integration test, container build, staging deployment with smoke tests, and manual approval for production. This ensures no code reaches production without passing all checks.

Tasks

• Build lint, unit test, integration test stages
• Implement container build and push to registry
• Build staging deployment with smoke tests
• Implement manual approval gate for production deployment

---

Epic: Salesforce Connector Production Readiness

Plan: Prepare the Salesforce connector for production by completing blocked endpoints, securing credentials, and implementing per-environment configuration.

Architectural Context: Some endpoints are blocked on Salesforce custom field creation. JWT private key must move from disk to Doppler. Per-environment credentials (separate connected apps for dev, staging, prod) prevent cross-environment contamination. Rate limiting and quota tracking ensure compliance with Salesforce governor limits.

Tasks

• Complete all endpoints blocked on Salesforce custom field creation
• Move JWT private key from disk to Doppler
• Implement per-environment credentials (separate connected apps for dev, staging, prod)
• Build rate limiting, quota tracking, and backpressure