The expected configuration file format by default is
json, but KrakenD can parse any of these file formats:
You can validate the syntax of any of these with
You are free to choose
toml or any of the other formats listed above at your best convenience. But have in mind the following limitations when choosing a file format that is not
json, as formats that need a proper indentation present more problems to control it (e.g.:
jsonformat, so it’s always more convenient to reuse snippets of code (copy and paste!).
--lintflag on the check command because expects json content to validate its schema (you could convert the file using a 3rd party tool though). You can still use the rest of the check commands.
As you can see, if you are OK with the limitations above, you can freely choose any other format.
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.