vyconf.git/src/config_tree.ml, branch rolling Software appliance configuration framework (mirror of https://github.com/vyos/vyconf.git) https://git.amelek.net/vyos/vyconf.git/atom?h=rolling 2024-10-28T01:50:41+00:00 T6718: update build system, drop batteries, and adjust for lib changes 2024-10-28T01:50:41+00:00 John Estabrook jestabro@vyos.io 2024-10-23T23:50:46+00:00 urn:sha1:5d7927e392e70436aaca1f8261e5d4ab8e4ec8f8 Update as needed for use with contemporary vyos1x-config: . update build system to use dune . drop use of batteries . update for protoc breaking changes in versions >= 3.0 . remove files now in vyos1x-config (config_tree et. al.; parsing) 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 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 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. Do not quote values that don't need quoting in Config_tree.render 2018-02-18T15:04:53+00:00 Daniil Baturin daniil@baturin.org 2018-02-18T14:54:46+00:00 urn:sha1:dc4bedee63c2c4d8c1dbd3c6aa9a12f4e072681b i.e. if they don't contain whitespace or characters of special significance to the parser (;[]{}#). Add Config_tree.render_at_level function for correct rendering of configs for human consumption. 2018-02-17T16:15:57+00:00 Daniil Baturin daniil@baturin.org 2018-02-17T16:15:57+00:00 urn:sha1:bfa93363f3e8533ef352cad38c2adfa21dbc28a3 The idea of the correct (for subsequent parsing) and familiar for all other purposes rendering: * When rendering the entire config, do not render the invisible "root" node, only render its children. * When rendering config at specified path, do not include any nodes that are within the path (e.g. if path "system login" exists, "show system" request output should start with "login {", not "system { login { ..."). T255: Add curly config renderer (#8) 2017-04-03T00:10:58+00:00 Shon Feder abathologist@gmail.com 2017-04-03T00:10:58+00:00 urn:sha1:9cd999ca97788988902913a5d8b86bbd1ac1cf71 * Add stand-alone config_tree renderer * Add tests for stand-alone config_tree renderer * Add renderer with reference tree * Add tests for Config_tree renderer with reftree * Update config files * Add refactoring functions and correct tests Add JSON de/serialization derivers to vytree and config tree modules. 2017-01-09T20:50:28+00:00 Daniil Baturin daniil@baturin.org 2017-01-09T20:50:28+00:00 urn:sha1:f947b3e8e7b9db2fcab250ce6d8050b650130cec