https://github.com/vyos/vyos-1x/pull/1019
https://github.com/vyos/vyatta-cfg/pull/41
https://github.com/vyos/vyatta-cfg-system/pull/171
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 30 2021
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.
Aug 19 2021
Aug 16 2021
Aug 13 2021
Aug 12 2021
Aug 11 2021
This will be merged, pending discussion on pros/cons of preprocessing vs. relaxing schema restriction.