Connecting services
Service connections were removed from ZopDay. Pass another service's address as an environment variable, and attach a database to a service from its Databases tab.
ZopDay no longer has service connections. The declared edges between two deployments, and the injectedVar field that copied one deployment’s URL into another, were removed, and their API endpoints no longer exist. The architecture canvas shows services and datastores but draws no edges between them.
Two features cover what connections were used for.
Point one service at another
Give the calling service the address as an ordinary environment variable. Open the service, go to Settings, and add the variable under Environment variables, for example API_URL. Use the target’s in-cluster Service address or its public URL. ZopDay does not track the target, so if its address changes, update the variable yourself.
Attach a database to a service
Open the service on the canvas, go to its Databases tab, and click + Add database. ZopDay creates a database and a scoped SQL user on a MySQL or PostgreSQL datastore connected to the infrastructure the service runs on, stores the password in your cloud’s secret manager, and records the connection variables on the service: DB_HOST, DB_PORT, DB_USER, DB_NAME, DB_DIALECT and DB_PASSWORD. A deploy then ships them, which restarts the service. DB_PASSWORD is kept as a secret reference and resolved only inside the deploy pipeline.
If those variable names are already taken on the service, ZopDay prefixes them with PG_ or MYSQL_, and Edit keys lets you rename them. Removing a database from the tab takes its variables off the service and redeploys it; the database itself stays on the datastore with its data.
Over MCP, the same actions are list_service_datastores, create_service_database and remove_service_database.