https://sonarly.com/issue/15848?type=bug
Workflow execution of logic functions fails because the worker process doesn't receive the LOGIC_FUNCTION_TYPE environment variable, causing it to default to DISABLED in production while the server process correctly receives LOCAL.
Fix: Added `LOGIC_FUNCTION_TYPE` and `CODE_INTERPRETER_TYPE` environment variable passthrough to both server and worker services in `docker-compose.yml`.
**Problem:** After commit f0c83434a7 changed the default `LOGIC_FUNCTION_TYPE` from `LOCAL` to `DISABLED` in production, self-hosted users who set `LOGIC_FUNCTION_TYPE=LOCAL` in their `.env` file couldn't get the value passed into their Docker containers because the variable wasn't listed in the `environment:` section of docker-compose.yml. This caused the worker process (which runs workflows) to use the `DisabledDriver`, while direct testing through the server process might work if the user manually added the env var only to the server config.
**Fix:** Added both `LOGIC_FUNCTION_TYPE: ${LOGIC_FUNCTION_TYPE}` and `CODE_INTERPRETER_TYPE: ${CODE_INTERPRETER_TYPE}` to both the server and worker `environment:` sections, following the same pattern as `STORAGE_TYPE` and other existing passthrough variables. This ensures both variables from `.env` are propagated to both containers.
**Note for Kubernetes/Terraform users:** The Terraform deployment files (`deployment-server.tf` and `deployment-worker.tf`) have the same gap — they don't include `LOGIC_FUNCTION_TYPE` or `CODE_INTERPRETER_TYPE` in their env blocks. K8s users would need to add these env vars to their deployment configurations manually.
Sonarly Claude Code
e6956ead47