add descriptive info that's independent of the transport

[terrillmoore]

I have a family of maintenance scripts (jumphost-gateway-tools).

With a large number of gateways, it's really important for those scripts to display the gateway description. However, the only info they have available is on the gateway itself.

If the gateway is using packet forwarder, I can extract the description from packet_forwarder local_conf.json .

But that information is not present when using other transports.

And anyway, it's a hack to look into the transports, we ought to have an extra file that has the config info that the scripts need.

Could we drop an extra file in /var/config/lora with "gateway_conf"."contact_email" and "gateway_conf"."description"? This would allow the scripts to find out what they need no matter the transport. You could call it gateway_info.json or similar.

If we do this, it would be really helpful to add another new key "gateway_conf"."transport", identifying the transport in use (semtech, basic_station, etc.) Right now the scripts must guess based on looking at the /etc/rc.d scripts. It's at best fragile.

[terrillmoore]

We still need the extra fields in the config directory of the gateway for basic settings, so the admin scripts can find out what's going on. Copying the .yaml file might be enough, but we'd need to flatten so that all the inherited values are passed through. A single extra JSON file would be fine. This is a genuine headache in operation, currently.