[DISPATCH-1659] Deprecate bespoke config file format for proper JSON

• Type: Wish
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.12.0
• Fix Version/s: 2.0.0, Backlog
• Component/s: Management Agent
• Assignee: Unassigned
• Reporter: Ken Giusti
• Created: 20/May/20 12:51
• Updated: 20/May/20 13:50

Description

The format of the qdrouterd.config file is not JSON compliant. Instead it is some bespoke quasi subset of JSON with custom comment syntax and whitespace formatting restrictions.

This bespoke format has (at least) two disadvantages:

1) users cannot leverage the plethora of JSON tooling available for config generation
2) increased development/maintenance effort to support the bespoke format.

This is a proposal to deprecate support for the non-JSON configuration file format in favor of a JSON compliant file format.