Skip to content

Single consumed service when expected multiple ones #12

@EndeavourGo

Description

@EndeavourGo

I was expecting to have more than one consumed service node when there are more than one provider for the requested service. If that is correct, it should be fixed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions