amadan
Config delivery doesn't render env files for kind:service unit-stamped routes Issue open
Migrated from github.com/carlosframework/platform issue #222, opened 2026-08-17. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: Config delivery renders no env file for kind:service unit-stamped routes.
---
Found during the Woodstar cutover (runbook PR #208, catch 2).
carlos env set -app woodstar-relay WOODSTAR_APPLE_APP_ID=… succeeded through the door, but no /etc/carlos/apps/woodstar-relay.bdm.oncarlos.com.env was ever rendered on the box, even though the route is unit-stamped (woodstar-relay.service) and the sweep runs. The same pass DID sweep away a hand-written /etc/carlos/apps/woodstar.env (no backing route/config), which is how the gap surfaced: a service-kind tenant currently has NO product-side way to get env into its unit — the interim fix was a unit-level Environment= line over SSM, exactly the box-local workaround the operate-via-API rule exists to eliminate.
Expected: a kind:service route with a stamped unit gets <host>.env rendered from its app's config bundle like kass's unit does, and the unit template convention (EnvironmentFile=-/etc/carlos/apps/<host>.env) then just works.
🤖 Generated with Claude Code