This is a high priority feature, and will likely be targeted as soon as possible after v17 ships, though it is not yet committed to a release.
Yes @MrMuishond, we can parse XML with a lot of languages in a quite easy way.
I'm Python developer and it's very easy to parse.
But the ideia, is for non developers, like network admins. They need to have the ability to easily read, identify and change what they need without needing to code.
YAML it's much more readable than XML.
Increasing the Idea, it would be a awesome feature if we can select a piece of exported text, change it locally on any text editor and than put it back on CLI interface to apply new configurations.
It would be much helpfull to configure and/or to deploy same configurations on different firewalls.
The Export configuration feature is quite good, but it's being exported as XML.
XML it's a rich text markup language but it's does not have a good readability.
I believe that the YAML markup language it's much more fast, efficient (to parse it inside when you're coding on any language) and easy to admins read and identify problems or do any other job directly on the configuration file.
The actual XML:
YAML Config would be:
Much more readable, no?
On larger configurations, we can see how YAML turns it better to read.