summaryrefslogtreecommitdiff
path: root/data/templates/container/storage.conf.j2
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2023-05-26 22:21:55 +0200
committerChristian Breunig <christian@breunig.cc>2023-05-27 08:57:12 +0200
commitec8ffd2c967d178c913be645c896434aa3212c9c (patch)
tree8b6df4cfa2ad2d4ca0fd570c47c685d8ec7d1295 /data/templates/container/storage.conf.j2
parent1395704d2692f2d57368e8cfa5b7b9e8791164cd (diff)
downloadvyos-1x-ec8ffd2c967d178c913be645c896434aa3212c9c.tar.gz
vyos-1x-ec8ffd2c967d178c913be645c896434aa3212c9c.zip
smoketest: T5242: automatically detect interface "capabilities"
Current state of vyos-1x smoketests have hardcoded features to test. The feature support is inside the base class BasicInterfaceTest class BasicInterfaceTest: class TestCase(VyOSUnitTestSHIM.TestCase): _test_dhcp = False _test_ip = False _test_mtu = False _test_vlan = False _test_qinq = False _test_ipv6 = False _test_ipv6_pd = False _test_ipv6_dhcpc6 = False _test_mirror = False All derived classes need to enable the tests that are supported on this interface type. Adding new feature to a given interface (like vif support in T5237) require manually enabling those tests for the given interface. It would make much more sense, if we can query the config backend for supported interface options - or in other words - is there a CLI node available that corresponds to set interfaces ethernet <name> vif - if that's the case, _test_vlan = True.
Diffstat (limited to 'data/templates/container/storage.conf.j2')
0 files changed, 0 insertions, 0 deletions