search

wmo-im / wis2box

WIS2 in a box is a reference implementation of a WMO WIS2 Node
https://docs.wis2box.wis.wmo.int
Apache License 2.0
40 stars 16 forks source link

add API endpoint with list of MQTT connections #137

Open tomkralidis opened 2 years ago

tomkralidis commented 2 years ago

A user should be able to determine which external PubSub services/topics a wis2box is subscribed to.

Options:

  1. an additional ad hoc API endpoint (say /mqp-brokers), hence the need for moving our pygeoapi setup to wis2box-api proper)
  2. create an API collection called mqp-brokers, which is populated with 1 GeoJSON per broker
  3. other options?

cc @petersilva

tomkralidis commented 2 years ago

Need to consider access control to access connectivity information (may need different views depending on auth).

petersilva commented 2 years ago

was discussed a bit in today's standup. There are multiple competing interpretations: are we:

  1. displaying a list of what MQP end points this node is subscribing to (simple status information)
  2. offering A list of MQP points known to be available (global list of end points this node could subscribe to?) for selection (to add subscriptions to the ones locally in use, for example)
  3. feeding a global list of active MQP endpoints (say we send out a message so that the global brokers and global cache "know" that this wis2nod exists.)

In case 3, we would define some subset of global brokers... and phone home... sending them a message saying "I exist"... This message is currently undefined.