Can't add multiple components to `metadata.yaml` for system test

[Fujikawas]

Met while working on #737, I would like to add both dumux-adapter and micro-manager to metadata.yaml for two-scale-deat-conduction case like:

  micro-dumux:
    participant: Micro-Manager
    directory: ./micro-dumux
    run: ./run.sh -l /home/precice/dumux
    component: 
      - dumux-adapter
      - micro-manager

Test shows that it can't read the component for this participant.

[MakisH]

I see the confusion, the documentation is wrong:

Component or list of components that this case depends upon (typically an adapter)

the italics part makes sense from YAML syntax perspective, but not from what this means for the test. Multiple components would mean multiple Docker services. This would need significant restructuring to work, and is not what you need.

It sounds like the micro-dumux is a different component built on top of the dumux component, and using both DuMux and the Micro-Manager. I would rather implement this in the Dockerfile.

[IshaanDesai]

It sounds like the micro-dumux is a different component built on top of the dumux component, and using both DuMux and the Micro-Manager. I would rather implement this in the Dockerfile.

micro-dumux requires dumux and pybind11, but not the Micro Manager.

[MakisH]

Still, pybind11 could go into an intermediate layer of dependencies, or it could be installed directly by the respective tutorial.

[IshaanDesai]

Still, pybind11 could go into an intermediate layer of dependencies, or it could be installed directly by the respective tutorial.

Yes, this makes sense.

[k4rtikx]

From the discussion above it seems the issue is not that metadata.yaml should support multiple components, but that the documentation suggesting “Component or list of components” is misleading.

Since multiple components would imply multiple Docker services which is not intended here, the correct approach appears to be installing additional dependencies such as pybind11 in the Dockerfile or tutorial setup rather than specifying multiple components in metadata.yaml.

I plan to submit a small documentation fix clarifying that component should refer to a single component and that additional dependencies should be handled in the Dockerfile or tutorial setup to avoid similar confusion in the future.