Feature #3036
closedupdate vty reference -- and make it so that it can be done without manual edits
100%
Description
osmo-bts has a number of variants: osmo-bts-trx, osmo-bts-sysmo, etc., and each may have some differing VTY commands.
The way we currently generate the vty reference PDF in osmo-gsm-manuals is that we launch the program and issue 'show online-help' on the vty; this outputs an XML of all VTY commands and their docs.
But how do we produce one VTY reference for all of the various BTS types?
Should we change osmo-gsm-manuals to produce N different VTY references, one for each BTS model?
Should we somehow combine all generated XMLs?
Decide on the above, generate the VTY reference for each BTS model and update osmo-gsm-manuals.git with it.
Furthermore, osmo-bts-* usually exits right away when there is no BSC to connect to. That's a bit cumbersome when all you want to do is generate the VTY reference XML. Maybe we can introduce a cmdline switch to generate the XML instead of going through the VTY?