vyos-1x.git - VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git)

Age	Commit message (Collapse)	Author
2019-10-24	[vyos.config] T1764: support both string and list arguments in config functions.	Daniil Baturin

2019-10-23	[vyos.config] T1758: check that config setup has completed before	John Estabrook
	calling showConfig, else, default to config.boot
2019-10-23	[vyos.config] T1758: use vyos.configtree for reading values,	Daniil Baturin
	instead of calling cli-shell-api.
2019-07-03	[vyos.config] T1505: correct return_effective_values output splitting.	Daniil Baturin

2019-06-13	T1431: make it possible to obtain session environment and run vyos.config ↵	Daniil Baturin
	functions under it. This is required for programs running outside a CLI session, like the future API daemon.
2019-05-28	T1397: Rewrite the config merge script	John Estabrook
	Add vyos.config.show_config to show working configuration. Add vyos.remote.get_config_remote() for obtaining remote config files.
2018-08-26	T801: correct parsing of returnValues and listNodes output.	Daniil Baturin

2018-06-20	Initial API documentation for vyos.config.	Daniil Baturin

2018-06-16	Set the license of all vyos.* libraries to LGPLv2+.	Daniil Baturin

2018-02-28	Fix return_values function (return a list instead of a raw string).	Daniil Baturin

2017-10-26	T433: Add "effective" observers and inSession to the vyos.config library	Taniadz

2017-09-08	Make the vyos.config.Config's return_value(s) and list_node functions behave ↵	Daniil Baturin
	like their Perl counterparts. Most scripts used to do something like my $foo = $config->returnValue("system foo"); if !defined($foo) { $foo = $defaultFooValue; } In most cases values do not exist because they are optional and simply not set. In a substantial minority of cases they don't exist but are mandatory, in this case it's probably a good practice to check if it exists first. In rare but frustrating cases returnValue returns undef because the path is wrong. It was tempting but as it turns out impractical to force the user to handle every undefined value as an error, but the cost of wrapping every return_value call in a try/except block is too high. Instead we should facilitate the most common case. For this, those functions now support an optional named argument default=None so an optional value with a sensible default can be handled like $foo = config.return_value("system foo", default="bar")
2017-09-08	Automatically decode the output of cli-shell-api as ASCII	Daniil Baturin
	to avoid having to decode it anywhere else.
2017-08-17	T353: add the Python library for reading VyOS config to the new package.	Daniil Baturin