vyos-1x.git/src/conf_mode/container.py, branch rollingVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling2026-06-16T18:24:44+00:00template: T8923: fix typo in function argument "formater" -> "formatter"2026-06-16T18:24:44+00:00Christian Breunigchristian@breunig.cc2026-06-16T18:24:44+00:00urn:sha1:51e6b967b1216853c2bd3bc3298639bd3382b5bcT8923: normalize "can not" to "cannot"2026-06-16T18:24:44+00:00Christian Breunigchristian@breunig.cc2026-06-16T18:24:44+00:00urn:sha1:fa853ed8f25b5b9bf396d6e819b2c6259e7f5f42
Replace two-word "can not" / "Can not" with "cannot" across comments,
ConfigError messages, CLI help text, and op-mode output.
Standard SNMP MIB files under mibs/ are left unchanged.
python: T8857: replace bare except clauses with except Exception in config scripts2026-05-13T12:56:50+00:00Yuriy Andamasovyuriy@vyos.io2026-05-13T12:56:50+00:00urn:sha1:d004a2b5caa9b819d93af897b1c218a2f3197c8b
Bare except: catches everything derived from BaseException, including
SystemExit and KeyboardInterrupt. Config scripts must not silently
continue past sys.exit(), so replace bare except: with except Exception:
in the three config-mode scripts that contained one.
Library code (python/vyos/configverify.py, python/vyos/config.py) and
op-mode scripts are intentionally out of scope: those cases require
case-by-case design review (e.g. MTU lookups should accept defaults as
arguments rather than rely on exception handling; reset-style op-mode
scripts may legitimately want to ignore KeyboardInterrupt).
Sites changed:
- src/conf_mode/interfaces_ethernet.py (MTU adapter lookup)
- src/conf_mode/vpp_interfaces_bonding.py (MAC validation)
- src/conf_mode/container.py x2 (IPv4 / IPv6 prefix lookup)
T8410: Fix typos and mistakes for operational and configuration commands2026-03-24T17:02:56+00:00Viacheslav Hletenkov.gletenko@vyos.io2026-03-20T16:41:24+00:00urn:sha1:bb2aee1e58c1cd30087b935798060e6bf3c698c8
Fix typos and mistakes in the commands and comments
No functional changes
Merge pull request #4826 from nvollmar/T79822025-12-05T10:21:38+00:00Viacheslav Hletenkov.gletenko@vyos.io2025-12-05T10:21:38+00:00urn:sha1:6795f106a581489148bffb61fdeb067ff81d2fe0
T7982: container: generate run arguments onceT7982: container: generate run arguments once2025-11-10T08:10:16+00:00Nicolas Vollmarnvollmar@gmail.com2025-11-01T21:11:24+00:00urn:sha1:c3184c404ded2ea5bb385d6184c88dd71025b230container: T7305: fix VRF loss when restarting pods2025-11-03T20:09:14+00:00Christian Breunigchristian@breunig.cc2025-11-02T08:30:05+00:00urn:sha1:ae6d3437dc3247c396444b7f65eb49a98b0dd800
Container networks are only started when there is at least one active consumer.
If a network is created without any attached containers, it does not need to be
assigned to a VRF yet.
When the last container in a pod is stopped, its associated container network
is removed. Upon container restart, the kernel recreates the network, but the
VRF assignment may be lost in the process.
This change ensures that all container networks are correctly reattached to
their designated VRFs when a pod restarts.
T6686: adds container health checks2025-10-23T18:32:14+00:00Nicolas Vollmarnvollmar@gmail.com2025-09-08T05:24:38+00:00urn:sha1:bd3070477804ed03e356d95e8c619fe7580b9231container: T7863: Add user-defined MAC option for containers (#4762)2025-10-02T21:52:06+00:00l0crian1143656816+l0crian1@users.noreply.github.com2025-10-02T21:52:06+00:00urn:sha1:31d0ac632882e0faf8334823acc0a29147d22cc0container: T7681: fix multiple name servers2025-09-16T15:01:46+00:00l0crian1ryan.claridge13@gmail.com2025-09-16T15:01:46+00:00urn:sha1:5c5d3a6b839b2a612fefb7d5f0443b80ceb156d0
- Fixed error with multiple name servers missing space between --dns options