Page MenuHomeVyOS Platform

Move component versions used for config migration purposes into vyos-1x
Closed, ResolvedPublicENHANCEMENT

Description

To determine whether a config file syntax matches the current config syntax version, right now VyOS uses files in /opt/vyatta/etc/config-migrate/current/
Each file lives in its own package now, so without a live system next to you, it's very hard to find what the current versions are.

It would be better to move them into a single file in a simple format (e.g. JSON) and add library functions and utilities for reading them.

Details

Difficulty level
Hard (possibly days)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Perfectly compatible
Issue type
Internal change (not visible to end users)

Event Timeline

dmbaturin triaged this task as Normal priority.
dmbaturin created this object with visibility "Public (No Login Required)".

Moving to 1.3.x, let's combine this with dropping pre-6.5 compatibility and removal of old migration scripts.

syncer renamed this task from Move component versions used for config migration purposes into vyos-1x to .Oct 18 2018, 6:05 AM
syncer changed the subtype of this task from "Task" to "Enhancement".Oct 20 2018, 7:10 AM
zsdc changed Difficulty level from Unknown (require assessment) to Hard (possibly days).Mar 11 2021, 2:21 PM
zsdc set Is it a breaking change? to Unspecified (possibly destroys the router).

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.

dmbaturin changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.Sep 3 2021, 12:00 PM
dmbaturin set Issue type to Internal change (not visible to end users).