fix(justfile): add ensure-env dependency to dev-clean #238
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/PMS-307-dev-clean-ensure-env"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
dev-clean was the only Compose-invoking teardown recipe without the ensure-env dependency. With .env absent (e.g. after a prior dev-clean removed it), Compose aborts interpolating the required ${VAR:?} variables in compose.dev.yml before the down subcommand runs, so volume/target/image cleanup never executes and teardown is non-idempotent.
Adding ensure-env recreates .env from the persistent .env.dev template before down, matching the sibling recipes down / dev-down / dev-sso-down. dev-clean-all inherits the fix transitively.
#PMS-307
dev-clean was the only Compose-invoking teardown recipe without the ensure-env dependency. With .env absent (e.g. after a prior dev-clean removed it), Compose aborts interpolating the required ${VAR:?} variables in compose.dev.yml before the down subcommand runs, so volume/target/image cleanup never executes and teardown is non-idempotent. Adding ensure-env recreates .env from the persistent .env.dev template before down, matching the sibling recipes down / dev-down / dev-sso-down. dev-clean-all inherits the fix transitively. #PMS-307