Document updated on Oct 28, 2018
The expected configuration file format by default is
json, but KrakenD can parse different formats if one of the following is found:
Nevertheless, our recommendation is to choose
Validate the syntax (not the logic) with
You are free to choose
TOML or any of the other formats at your best convenience. But have in mind the following logic when choosing a file format other than
Using the UI: If you intend to generate or edit your configuration file using the KrakenDesigner, the input and output are always a
Flexible Configuration: If you want to split the configuration file into different pieces or use variables inside the configuration, the flexible configuration needs
Documentation: All our examples in the documentation and repositories are today shown in
JSON format, so it’s always more convenient to reuse snippets of code.
The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.