Support setting queue,hidden as exported port metadata

noflo / noflo-runtime-msgflo

NoFlo runtime for AMQP/MQTT

10 stars 8 forks source link

Open jonnor opened 9 years ago

jonnor commented 9 years ago

Right now have to use the programmatic API, or noflo-runtime-msgflo --option=inports.in.queue=foo

Using port metadata, would allow it to be visualized and edited in Flowhub, and be less verbose setup

jonnor commented 9 years ago

Or perhaps queue name should only be in the outer (msgflo) graph definition? In which case it would be edge metadata?