using `--process-compose-file` to merge configurations fails

[jay-aye-see-kay]

What happened?

Using the --process-compose-file flag to merge configurations fails, if no merging config this doesn't seem to be an issue

❯ devbox services up --process-compose-file process-compose.extras.yaml
Info: Ensuring packages are installed.
✓ Computed the Devbox environment.
Lockfile is up to date, resolution step is skipped
Already up to date
Done in 252ms
Info: Package "process-compose@1.64.1" already in devbox.json
Info: Package "process-compose@1.64.1" was already in devbox.json and was not modified
Info: Ensuring packages are installed.
✓ Computed the Devbox environment.
Starting all services: <...> 
25-09-16 15:52:29.381 FTL error="project /Users/jack/code/my-porject/process-compose.yaml is already specified in files to load"
Process-compose was terminated remotely, exit status 1

Steps to reproduce

1. Create a process-compose.yaml file
2. Create a second process-compose.extras.yaml file that overrides some of the config defined in the main one (i.e set is_disabled: "false")
3. run devbox services up --process-compose-file process-compose.extras.yaml and see error message above instead of running services

Command

services

devbox.json

Devbox version

0.16.0

Nix version

nix (Nix) 2.26.2

What system does this bug occur on?

macOS (Apple Silicon)

Debug logs

No response

[janbiasi]

@jay-aye-see-kay have you tried to use the available --pcflags? We're currently using it this way and it works without any issues, for example:

devbox services up --pcflags -f=process-compose.extra.yml

The code also implies that you can specify multiple -f files.