unify mqtt message `thing-creation`
The thing-creation message is a mess.
It would be much easier if the mqtt message for thing-creation
[1] always contain the same unique fields and not create some sections conditionally.
Especially the parsers
, default_parser
, properties
(of what) change a lot depending of the ingest type. The parser of a MQTT ingest message have nothing to do with the parser of a SFTP ingest message, but both use the same field.
It would be much easier if each field has a unique purpose instead of reusing it for different purposes.
In the parser case from above we would have a mqtt_parser
field and a sftp_parser
field. Or use something like
{
mqtt: { user: ..., passw: ..., default_parser: ... , parser: [...] , ...}
sftp: { user: ..., passw: ..., default_parser: ... , parser: [...] , ... }
ext_sftp { ... }
}
[1] which is generated in tsm/utils/get_json_config()