ipspace
Cleanup .vagrant directory when 'netlab down --cleanup' is used
When using Vagrant boxes, a .vagrant directory is created. Disk images for the vms get removed, but the directory itself remains
If there are concerns around deleting non-Netlab related files, we could consider renaming .vagrant to .netlab.vagrant
Nobody complained in the four years we're using Vagrant, so I guess this is not a high priority (as opposed to all the visible stuff Ansible and containerlab leave behind)
I'm worried about what might happen if vagrant fails to shut down nodes and then we remove stuff it needs. Containerlab is a different story because you cannot remove its files (they are owned by root).
The only safe way I can see to do this is to remove .vagrant directory only if (A) the lab used libvirt provider and (B) vagrant down succeeded, which makes libvirt provider the "natural" place to do the cleanup.