The /etc/snips.toml file is where a lot of central configuration options live for snips (e.g. which MQTT host to use). The file is in toml[1] format.
The snips actions-template system presumes that the action's config file will be a ini file (and is read by the ConfigParser module).
ConfigParser doesn't like importing toml files. For instance is throws ParsingError() when there's a space at the start of the line, and doesn't expect strings to be within quotes.
Using two different configuration systems means configs can't be shared (with a lot of manually-added boilerplate to read the toml file). It would be good to standardize, so that actions can easily read the same configs the snips daemons are using.
The
/etc/snips.toml
file is where a lot of central configuration options live for snips (e.g. which MQTT host to use). The file is intoml
[1] format.The snips actions-template system presumes that the action's config file will be a
ini
file (and is read by theConfigParser
module).ConfigParser
doesn't like importingtoml
files. For instance is throwsParsingError()
when there's a space at the start of the line, and doesn't expect strings to be within quotes.Using two different configuration systems means configs can't be shared (with a lot of manually-added boilerplate to read the
toml
file). It would be good to standardize, so that actions can easily read the same configs the snips daemons are using.[1] https://en.wikipedia.org/wiki/TOML