George Silvis, III
George Silvis, III
Also `network_delete`
What should happen if we run init_db with the Dell driver, then change the dell driver's VLAN config, then run init_db again? I don't think there's any very reasonable behavior...
The trunk port is a real problem here---right now the HaaS never touches it at all.
I think an easier solution may be to have a special journal entry "apply entire database"
`ip` can make bridges, too, btw
I've argued before that VLANs should be added to and removed from the pool with API calls rather than the config file. But the behavior here is fairly non-obvious. What...
Yeah, refusing to delete is in line with most other HaaS commands.
If we can use structured JSON, I don't see any good reason to change the fields we have. Just getting rid of the sentinel values should be sufficient, I'd say....