Enhance VirtualDevicePool

[rbino]

• Allow passing interfaces in the configuration instead of loading them from disk
• Allow dynamic registration of new devices

Open discussion point: where do we store the credential secret of newly registered devices?

[drf]

Open discussion point: where do we store the credential secret of newly registered devices?

Do we even need to do that? In my mind, if a Device is declared as a Virtual Device, it should be denied access from any transport and go straight into DUP queues. I reckon this might pose a limitation to a Device being tied to a single Flow (but maybe this can be circumvented somehow? Or do we assume that 2nd steps on a Virtual Device would be done through Flow interfaces, which kind of makes sense?), but preventing usage of a Virtual Device from outside Flow itself seems like the most logical solution to me.

[rbino]

Your point is totally valid, but we still have to support the Edge case, which implies the standard registration mechanism since we can't access in-cluster Rabbit queues