haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove customize action, this will need rethinking

This commit is contained in:
Mitchell Hashimoto 2011-12-21 15:24:43 -08:00
parent 7a70755362
commit 177eb828af
3 changed files with 0 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
lib/vagrant/action/builtin.rb
View File

@ -29,9 +29,6 @@ module Vagrant
use VM::ShareFolders
use VM::HostName
use VM::Network
# TODO: Bring back some sort of "customize" feature.
# use VM::Customize
# use VM::Modify
use VM::Boot
end
end

26
lib/vagrant/action/vm/customize.rb
View File

@ -1,26 +0,0 @@
module Vagrant
module Action
module VM
class Customize
def initialize(app, env)
@app = app
end
def call(env)
if !env[:vm].config.vm.proc_stack.empty?
# Create the proc which runs all of our procs
proc = lambda do |vm|
env[:ui].info I18n.t("vagrant.actions.vm.customize.running")
env[:vm].config.vm.run_procs!(vm)
end
# Add it to modify sequence
env["vm.modify"].call(proc)
end
@app.call(env)
end
end
end
end
end

37
lib/vagrant/action/vm/modify.rb
View File

@ -1,37 +0,0 @@
module Vagrant
module Action
module VM
# This class allows other actions on the virtual machine object
# to be consolidated under a single write lock. This vastly speeds
# up modification of virtual machines. This should be used whereever
# possible when dealing with virtual machine modifications.
class Modify
include Util::StackedProcRunner
def initialize(app, env)
@app = app
# Initialize the proc_stack, which should already be empty
# but just making sure here.
proc_stack.clear
# Create the lambda in the environment which is to be called
# to add new procs to the modification sequence.
env["vm.modify"] = lambda do |*procs|
procs.each { |p| push_proc(&p) }
end
end
def call(env)
# Run the procs we have saved up, save the machine, and reload
# to verify we get the new settings
run_procs!(env[:vm].vm)
env[:vm].vm.save
env[:vm].reload!
@app.call(env)
end
end
end
end
end