This brings up an interesting issue: validate_value.ml could easily be modified to print warnings, while maintaining T2759 (namely, only print fatal errors if _all_ validators fail for a given setting), however, is this reasonable behaviour ? One would think that a 'validator' is either pass or fail, and if it is just giving a warning, it is no longer a validator.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 15 2021
Nov 12 2021
I will take a look; thanks for the report !
Nov 7 2021
Nov 5 2021
@adestis there were discussions on this in the past week --- I will be helping @dmbaturin with the task
Oct 14 2021
Oct 1 2021
Note that the set commands above have already mangled the name --- no_tag_node_value_mangle is there to preserve names as follows:
Sep 30 2021
A few quick tests would suggest that this is specific to vrrp: though not exhaustive, of course, several examples of setting tag-node values in paths other than vrrp work as expected.
Sep 28 2021
Sep 27 2021
In testing:
https://github.com/vyos/vyos-1x/compare/current...jestabro:interface-names
https://github.com/vyos/vyatta-cfg/compare/current...jestabro:interface-names
The following removes legacy code: vyatta_net_name, vyatta_interface_rescan, XorpConfigParser
https://github.com/vyos/vyatta-cfg-system/compare/current...jestabro:interface-names
Sep 23 2021
Sep 6 2021
Sep 2 2021
Aug 30 2021
@stepler on a fresh installation, all migration scripts will be run, as the default config contains no component version string, and has to be incrementally migrated.
I will push to have a solution included in 1.3, reviewing both zsdc's and rps's suggested patches; we will not hold up epa1 for this, but rather include as a bug fix following.
A careful analysis of the error here is provided in the last two comments; the general question of unicode support will be investigated in T3785.
This is resolved for 1.3, and is not a backport candidate for 1.2, as indicated above.
cmd = {"op": "delete", "path": ["protocols","static","route", subnet, "next-hop", nexthop]}passed via the http-api properly returns the same error message as would be seen on the CLI. Non-issue.
The revisions in T3768/T1950 provide a listing of components in /usr/share/vyos/component-versions.json for easy reference; this file is not used during migration, so any changes to the file will have no effect. The larger issue of dropping reliance on vyatta-cfg-system for component version information will be handled in T3474 for those components that have been moved to XML/Python.
T3785 is opened for the general issue; a workaround will be provided in the interim.
Aug 21 2021
Aug 20 2021
The json file containing the system component version information was previously an artifact of the XML syntaxVersion implementation; with revisions to the latter in place for 1.4, and initial implementation removed for 1.3, the json file will now be dumped during migration.