mw stack deploy interprets list syntax for envs incorrectly

[LukasFritzeDev]

Describe the bug
docker compose supports two ways of defining environment variables: List and mapping syntax.

Bei ihm heißt es z.B.:

        environment:
            - POSTGRES_DB=${CORE_POSTGRES_DB}
            - POSTGRES_USER=${CORE_POSTGRES_USER}
            - POSTGRES_PASSWORD_FILE=/secrets/password.txt
            - POSTGRES_HOST_AUTH_METHOD=scram-sha-256
            - POSTGRES_INITDB_ARGS=--auth-host=scram-sha-256

        environment:
            POSTGRES_DB: "${CORE_POSTGRES_DB}"
            POSTGRES_USER: "${CORE_POSTGRES_USER}"
            POSTGRES_PASSWORD_FILE: "/secrets/password.txt"
            POSTGRES_HOST_AUTH_METHOD: "scram-sha-256"
            POSTGRES_INITDB_ARGS: "--auth-host=scram-sha-256"

These two should be equivalent. But if the List syntax is used the following envs are set up:

0=POSTGRES_DB=REDACTED
1=POSTGRES_USER=REDACTED
3=POSTGRES_PASSWORD_FILE=/secrets/password.txt
3=POSTGRES_HOST_AUTH_METHOD=scram-sha-256
4=POSTGRES_INITDB_ARGS=--auth-host=scram-sha-256

Since there is now a backend validation to prevent this behaviour, this syntax is broken.

To Reproduce
Steps to reproduce the behavior:

1. use mw stack deploy with a compose file that uses list syntax
2. Command faiis with validation error

Expected behavior
Command works and envs are imported correctly

Console logs
If applicable, add console outputs to help explain your problem.

Environment (please complete the following information):

• OS: macOS 26.2
• Shell zsh
• Terminal
• Version (output of mw --version): @mittwald/cli/1.12.0 darwin-arm64 node-v20.19.3

[gandie]

I think i've caught the bug. Wrote a test to show the underlying issue. Assume we have file like this:

services:
  webapp:
    environment:
      something: "little"
      bit: "of love"

This works fine. But with a file like this:

services:
  webapp:
    environment:
      - something=little
      - bit="of love"

We run into an issue that looks familiar to what you have noticed, only a little earlier in the control flow i guess. Test output to show the issue:

 FAIL  src/lib/resources/container/containerconfig.test.ts
  ● Containerconfig handling › Environment parsing from docker compose files › call stack file parser list syntax

    expect(received).toMatchObject(expected)

    - Expected  - 4
    + Received  + 4

      Object {
        "services": Object {
          "webapp": Object {
    -       "environment": Object {
    -         "bit": "of love",
    -         "something": "little",
    -       },
    +       "environment": Array [
    +         "something=little",
    +         "bit=\"of love\"",
    +       ],
          },
        },
      }

      52 |         }
      53 |       );
    > 54 |       expect(res).toMatchObject({
         |                   ^
      55 |         services: {
      56 |           webapp: {
      57 |             environment: {

      at Object.<anonymous> (src/lib/resources/container/containerconfig.test.ts:54:19)

This array probably resolves to tuples of array index and element further down the line, that's what you've seen i guess.

My fix for this is very crude right now, as i've just sneaked in some detection for environment being an array, adjusting towards environment object on the fly if found.

Next week i can beautify my fix, although it might take some more refactoring to get those loader and parser code passages in line. Function names in loader.ts are strange imo, e.g. loadStackYAMLFromFile vs. loadStackFromFile . Maybe there is even some library that might help here? Writing such parser code manually tends to be very error-prone and needs lots of testing.