Delphi v0.9.12
Delphi v0.9.12 is a patch release focused on safer operations and cleaner platform workflows. It improves TelAPI health checks, Flow Builder version management, TOBi webhook validation, setup seeding, TLS CA bundle configuration for database and Redis clients, and logging behavior for shared services.
v0.9.12Recommended SDKv0.1.3Supported SDK range>=0.1.2 <0.2.0Highlights
- Improved deployment promotion reliability and release workflow handling.
- Simplified TelAPI readiness with a single Redis-backed
GET /healthendpoint. - Added Flow Builder draft deletion from Version History.
- Tightened Vodafone TOBi callback token handling to use the
tokenheader only. - Split database and Redis TLS CA bundles into separate operator-facing settings.
- Improved logging defaults and image rebuild detection for services that depend on the shared logger package.
Flow Builder
Flow Builder now supports deleting draft versions from Version History. After a draft is deleted, the builder refreshes the active draft, version list, and published flow data together so users return to a consistent state.
The UI also hides WebRTC test-call controls and Browser endpoint settings when WebRTC phone capability is disabled, while keeping browser actions available where supported.
API and webhooks
TelAPI now uses one minimal health endpoint:
GET /healthreturns200when required dependencies are reachable.GET /healthreturns503when Redis readiness fails.
Swagger documentation loading was also fixed for the browser CSP policy.
Vodafone TOBi callbacks now validate the per-conversation callback token from the token header only. Trace correlation values can still be supplied on the callback URL as query parameters.
Platform setup
Automatic container startup now runs baseline seed data only. First-use setup, upgrade steps, and dev/test data are handled through the delphi-setup CLI.
If you need local or test seed data, run docker exec -it voiceai-telweb delphi-setup --dev-seeds from an interactive TTY. Non-interactive --dev-seeds now fails clearly instead of applying dev data during automation.
Infrastructure
Database and Redis client trust bundles are now configured separately:
DATABASE_SSL_CA_BUNDLE_B64materializes the database CA bundle at/etc/ssl/database/ca.crt.REDIS_TLS_CA_BUNDLE_B64materializes the Redis CA bundle at/etc/ssl/redis/ca.crt.DATABASE_SSL_CA_FILEdefaults to/etc/ssl/database/ca.crt.REDIS_TLS_CA_FILEdefaults to/etc/ssl/redis/ca.crt.
Shared service logging now keeps pretty output behind an explicit pretty option or an interactive TTY check, which keeps container logs structured by default. CI build detection also treats packages/logger changes as rebuild triggers for TelAPI, Scaler, and Tasker images.
INTERNAL_CA_CRT_B64 remains supported as a compatibility fallback for existing deployments, but new app-service configuration should use DATABASE_SSL_CA_BUNDLE_B64 and REDIS_TLS_CA_BUNDLE_B64.
For verified PostgreSQL TLS, set DATABASE_SSL_MODE=verify-ca or verify-full and provide DATABASE_SSL_CA_BUNDLE_B64. For Redis TLS with a private CA, provide REDIS_TLS_CA_BUNDLE_B64. ElastiCache deployments using Amazon-signed certificates can continue to rely on the system CA store.
Upgrade checklist
- Point health checks and load balancers at
GET /health. - Migrate app-service CA secrets from
INTERNAL_CA_CRT_B64toDATABASE_SSL_CA_BUNDLE_B64and/orREDIS_TLS_CA_BUNDLE_B64. - Use
delphi-setup --apply-missingfor platform update steps after deployment. - Use interactive
delphi-setup --dev-seedsonly when dev/test seed data is intended.
SDK compatibility
| Component | Version |
|---|---|
| Platform | v0.9.12 |
| Recommended TelPhi SDK | v0.1.3 |
| Supported SDK range | >=0.1.2 <0.2.0 |
See the SDK section for installation and the per-version compatibility matrix.