.env File Support for kraft cloud deploy Command

[guillempuche]

Currently, kraft cloud deploy does not support the --env-file flag or accept a standard .env file for injecting multiple environment variables. Instead, users must manually supply each variable by using the -e KEY=VALUE flag multiple times, which is cumbersome for projects with many configs.

How it’s done now:

kraft cloud deploy \
  --kraftfile infrastructure/kraftcloud/caddy/Kraftfile \
  -M 1G \
  -e KEY1=VALUE1 \
  -e KEY2=VALUE2 \
  .

Alternatively, you can export your .env file into your shell environment before running the command:

set -a
. infrastructure/kraftcloud/.env
set +a

kraft cloud deploy ... 

However, both methods lack the simplicity and cleanliness of passing a file directly.

Idea:
Add a --env-file <path> flag to kraft cloud deploy, similar to Compose and Docker, to streamline multi-variable workflows and align UX across CLI commands.

kraft cloud deploy \
  --kraftfile infrastructure/kraftcloud/caddy/Kraftfile \
  --env-file infrastructure/kraftcloud/.env \
  -M 1G \
  .

Benefits:

• Cleaner configuration management
• Lower manual error risk
• More familiar developer experience