vagrant/test/unit
Seth Vargo 5a4f345363
Use Util::Tempfile when configuring networks
This fixes a fairly large tempfile leak. Vagrant uses a template
renderer to write network configuration files locally to disk. Then,
that temporarily file is uploaded to the remote host and moved into
place. Since Vagrant is such a short-lived process, GC never came along
and cleaned up those tempfiles, resulting in many temporary files being
created through regular Vagrant usage.

The Util::Tempfile class uses a block to ensure the temporary file is
deleted when the block finishes. This API required small tweaks to the
usage, but provides more safety to ensure the files are deleted.
2016-05-28 23:22:34 -04:00
..
plugins Use Util::Tempfile when configuring networks 2016-05-28 23:22:34 -04:00
support Add unique names to all tmpdir and tempfile calls in tests + cleanup 2016-05-28 23:22:34 -04:00
templates/guests SUSE-flavored systems uses STARTMODE and not ONBOOT 2015-11-08 16:09:04 +01:00
vagrant Add unique names to all tmpdir and tempfile calls in tests + cleanup 2016-05-28 23:22:34 -04:00
base.rb Add unique names to all tmpdir and tempfile calls in tests + cleanup 2016-05-28 23:22:34 -04:00
vagrant_test.rb Add a function to get to the "original" environment with Vagrant 2015-07-09 12:34:04 -06:00