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 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) 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 2017-01-20T16:56:32+00:00 Daniil Baturin daniil@baturin.org 2017-01-20T16:56:32+00:00 urn:sha1:46efea7823acfef5230f33f4b27c99bc176aafbc If we are going to use batteries for numeric_compare, why not take advantage of the rest. 2017-01-17T13:17:21+00:00 Daniil Baturin daniil@baturin.org 2017-01-17T13:17:21+00:00 urn:sha1:ff4a0f824b33dfce8010d0ba4a6075369bbfec94 Findlib package "vyconf" now contains modules required for working with configs, namely Vytree, Config_tree, Reference_tree, Valur_checker, Curly_lexer, and Curly_parser. Renderer will go there too. Migration scripts and convertors/analyzers/whatever utilities that need to read and write config files will link with it. The "vyconf.vyconf-config" package is for working with vyconfd.conf config. Config scripts written in OCaml, the shell, and the non-interactive client can use it to read the system config if the user didn't use options for socket location and so on. The "vyconf.vyconf-client" package is for the Protobuf over UNIX sockets protocol clients. 2017-01-17T07:01:41+00:00 Daniil Baturin daniil@baturin.org 2017-01-17T06:59:19+00:00 urn:sha1:c4d8a6e4621133e9d65084e84fe5fa0ea63253d4 2017-01-16T17:59:35+00:00 Daniil Baturin daniil@baturin.org 2017-01-16T17:59:35+00:00 urn:sha1:89e2f647c8a69105cba18f6eef333bc395812e10 2017-01-16T13:07:50+00:00 Daniil Baturin daniil@baturin.org 2017-01-16T13:07:50+00:00 urn:sha1:f8b5879fed1d5185a931206fd2784825567947ae Right now it uses a SHA-1 sum of 30 random bits. I hope that's secure enough. 2017-01-16T07:42:26+00:00 Daniil Baturin daniil@baturin.org 2017-01-16T07:42:26+00:00 urn:sha1:482321db949bf5b5b6868a3fc8cbeaaa589578e2 2017-01-15T16:07:39+00:00 Daniil Baturin daniil@baturin.org 2017-01-15T16:07:39+00:00 urn:sha1:291a998ca375077b3c23c1e3c43a7fc206c8de4b The Message module contains read and write functions that take care of the wire protocol, which sends a 4 byte length header before every message. They take a bytes buffer and don't care about its contents. The Vyconf_client module has high level functions for interfacing with vyconfd. Functions for creating a socket and creating a server loop are in Startup. The rest is, for now at least, right in vyconfd. Notes: Message.read/write probably should be wrapped in Lwt_io.atomic We need to find out if it's safe to reuse Pbrt.Encoder.t or we really should create it every time. 2017-01-09T20:50:28+00:00 Daniil Baturin daniil@baturin.org 2017-01-09T20:50:28+00:00 urn:sha1:f947b3e8e7b9db2fcab250ce6d8050b650130cec