[bug] volume not generated

[naruse666]

Describe the bug
I defined a simple volume and generated compose.yaml.
But compose.yaml does not contain volumes.

score.yaml

apiVersion: score.dev/v1b1

metadata:
  name: hello-world
containers:
  awesome-web-service:
    image: busybox
    command: ["/bin/sh"]
    args: ["-c", "while true; do echo Hello!; sleep 100; done"]
    volumes:
    - source: ${resources.tmp-data}
      target: /tmp

resources:
  tmp-data:
    type: volume

generate compose.yaml

score-compose run -f score.yaml -o compose.yaml

compose.yaml

services:
  hello-world:
    command:
      - -c
      - while true; do echo Hello!; sleep 100; done
    entrypoint:
      - /bin/sh
    image: busybox
    volumes:
      - type: volume
        source: tmp-data
        target: /tmp

Expected behavior

services:
  hello-world:
    command:
      - -c
      - while true; do echo Hello!; sleep 100; done
    entrypoint:
      - /bin/sh
    image: busybox
    volumes:
      - type: volume
        source: tmp-data
        target: /tmp
volumes:       # generated this block
  tmp-data:    #

Desktop (please complete the following information):

• OS: macOS
• Version [e.g. 1.1.0]

Additional context
I'm a newbie to Score, so my thinking may be wrong.

[astromechza]

Unfortunately score-compose doesn't setup these volumes for you because score cannot predict what kind of volume is needed or how to provision it (which driver, or options).

Instead it relies on you setting up a separate compose.yaml file with the volume:

volumes:
  tmp-data:

And then including that when you run compose up: docker compose -f compose.yaml -f score.compose.yaml up.

We are looking into how we can support this better in the future and how we can pre-provision resources during the compose generation step.

[astromechza]

I'm going to close this as expected behavior. But we will make this better in the future.