a933b20d6f
Signed-off-by: Neetha John <nejo@microsoft.com> Why I did it Storage T0's have all vlan members as tagged How I did it Since currently minigraph does not have a unique way to identify if a vlan member is tagged/untagged and to ensure other scenarios are not broken, the logic used is to just update the vlan member type as 'tagged' when we determine that it is a storage backend device. This change will apply only to storage backend T0's since storage backend T1's will not have vlan member information How to verify it Updated the storage backend T0 testcases to check for tagged vlan members Added testcase to check if a T1 and backend T1 device generates an empty vlan member table Existing vlan member testcases are good enough for checking if any regression has been caused for regular T0's Build sonic_config_engine-1.0-py3-none-any.whl successfully |
||
|---|---|---|
| .. | ||
| data | ||
| tests | ||
| __init__.py | ||
| .gitignore | ||
| config_samples.py | ||
| lazy_re.py | ||
| MANIFEST.in | ||
| minigraph.py | ||
| openconfig_acl.py | ||
| portconfig.py | ||
| redis_bcc.py | ||
| setup.py | ||
| sonic-acl-extension.yang | ||
| sonic-cfggen | ||