vyconf.git, branch v0.1 Software appliance configuration framework (mirror of https://github.com/vyos/vyconf.git) https://git.amelek.net/vyos/vyconf.git/atom?h=v0.1 2019-01-24T20:26:04+00:00 Update README.md 2019-01-24T20:26:04+00:00 Christian Poessinger christian@poessinger.com 2019-01-24T20:26:04+00:00 urn:sha1:d6d3a1d2752d3252f874487668e7109b8c87f382 README: update build instructions 2019-01-20T21:15:01+00:00 Christian Poessinger christian@poessinger.com 2019-01-20T21:15:01+00:00 urn:sha1:0f121c12a842002961d0be4dd4287816d5c89be5 Adjust the build for latest Lwt and README for latest OCaml. 2019-01-19T14:33:58+00:00 Daniil Baturin daniil@baturin.org 2019-01-19T14:33:58+00:00 urn:sha1:af9ffaaa4a62c9266890c592e3b2f2ce5fb28a3e Escape special characters inside value strings when converting configs to commands. 2018-11-29T00:57:27+00:00 Daniil Baturin daniil@baturin.org 2018-11-29T00:57:27+00:00 urn:sha1:1ebea2e6914e5d2c4f07654bdbd489aa2c1ce165 Add support for node renaming. 2018-09-02T11:03:12+00:00 Daniil Baturin daniil@baturin.org 2018-09-02T11:03:12+00:00 urn:sha1:d33442c2576793420802bbd54127923079c487c4 Use String.concat instead of reinventing it with fold. 2018-06-05T20:16:49+00:00 Daniil Baturin daniil@baturin.org 2018-06-05T20:16:49+00:00 urn:sha1:05b086a782eeee8c2b0566660d942ec0909da6fb Add a function for getting sorted children from a node and use it for sorting set commands. 2018-06-05T09:35:12+00:00 Daniil Baturin daniil@baturin.org 2018-06-05T09:35:12+00:00 urn:sha1:335560d2c0420a363942d3368dec0b04dd8bf62b Initial implementation of the commands formatter. 2018-06-04T16:20:57+00:00 Daniil Baturin daniil@baturin.org 2018-06-04T16:20:57+00:00 urn:sha1:7f26d95164265b0ffd345afd510bf03ee98cd1d8 Expose missing exceptions from Config_tree in the module interface. 2018-05-23T12:24:58+00:00 Daniil Baturin daniil@baturin.org 2018-05-23T12:24:58+00:00 urn:sha1:fb6d3f6dfdbc3601a9af99263ec233bbd3a46e50 Render valueless nodes correctly. 2018-05-23T10:03:25+00:00 Daniil Baturin daniil@baturin.org 2018-05-23T09:57:20+00:00 urn:sha1:f0ed6868a5896dfde3d6519c1068f5e5dfea0417 The canonical format for valueless nodes is "foo;". There are two cases: when it's known from the reference tree that a node is valueless, we should render it the canonical way. However, a valueless node is not the same as a normal node with no children, semantically, so nodes that are note valueless should be rendered as "foo {}". If the reference tree is not present, resort to rendering all nodes without values as if they were normal nodes with no children rather than as if they were valueless. The parser is unaware of the distinction, so there are no implications for it.