We're already affected by this issue:
In the screenly-client snap we have two plugs for the one
udisks2:service slot and we're getting
auto connect udisks2:service (slot auto-connection), candidates found: "screenly-client:udisks2, udisks2:client"
In this particular case we want both of them to connect to the slot.
In the other situation - we have three dbus slots and three dbus plugs, and each plug should be connected to its own slot. Currently, the system tries to connect to all of them and we're getting the error message:
auto connect screenly-client:command-dbus-client (plug auto-connection), candidates found: "screenly-client:command-dbus-server, screenly-client:ping-dbus-server, screenly-client:playlist-dbus-server"
Is would be nice to have a way to select target slots for plugs in the snapcraft.yaml or in the snap's declaration.