Unclear error when COMPOSE_FILE has an empty entry #955

New Issue

2026-10-21T09:01:37Z

mayel commented

2026-10-21 09:01:37 +00:00

An app env with an empty COMPOSE_FILE entry, for example COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml" with no base value set, makes deploy fail with:

FATA <app/deploy.go:140> read .abra/recipes/bonfire/: is a directory

Nothing in that message points to COMPOSE_FILE or the env file. Could GetComposeFiles catch empty entries and say so? Something like COMPOSE_FILE has an empty entry (leading, trailing or double ":") in <env path>.

An app env with an empty COMPOSE_FILE entry, for example `COMPOSE_FILE="$COMPOSE_FILE:compose.postgres.yml"` with no base value set, makes deploy fail with: `FATA <app/deploy.go:140> read .abra/recipes/bonfire/: is a directory` Nothing in that message points to COMPOSE_FILE or the env file. Could GetComposeFiles catch empty entries and say so? Something like `COMPOSE_FILE has an empty entry (leading, trailing or double ":") in <env path>`.

🚀 1

decentral1se added the bug label 2026-10-21 14:36:21 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#955