9 Commits

Author	SHA1	Message	Date
Peter Eisentraut	901d3ad23b	Check exit codes of puppet provisioners ... Previously, failures in applying the puppet manifests would be ignored, because puppet apply/agent don't have any useful exit codes by default. (Errors are printed, but vagrant continues.) Use the option --detailed-exitcodes of puppet apply/agent to check for success.	2012-10-08 15:22:30 -04:00
Mitchell Hashimoto	b328e95045	Make puppet provisioner work with latest machine changes. ... Specifically it was still reference env[:vm] which is now `env[:machine]`.	2012-08-20 12:13:04 -07:00
James Turnbull	97420a990a	This commit has three minor changes to the Puppet provisioners: ... * Renamed the run_puppet_client method in the puppet provisioner to clarify it's function running Puppet in apply mode from the command line. * Renamed the run_puppet_client method in the puppet server provisioner to clarify the agent is being run. * Changed the Puppet server provisioner to use the more standard Git-style command line structure. The puppetd binary has been deprecated in favour of puppet with the agent flag.	2012-07-11 13:59:20 -04:00
Mitchell Hashimoto	55528e051c	Move provisioners to Vagrant.plugin("1", :provisioner)	2012-06-26 16:04:51 -07:00
Mitchell Hashimoto	590f648fc0	Built-in plugins use Vagrant.plugin("1", :config)	2012-06-26 16:02:44 -07:00
Mitchell Hashimoto	2e00a007ce	Move provisioner superclass into the V1 namespace	2012-06-26 15:06:04 -07:00
Mitchell Hashimoto	41bc8e7454	Move Config::V1::Base to Vagrant::Plugin::V1::Config	2012-06-24 17:06:11 -07:00
Jens Braeuer	ae92895411	Fix problem that Puppet module-paths were re-ordered by Vagrant. ... Puppet module-path were re-ordered by Vagrant due to the use of a hash. This could lead to unpredictable results.	2012-06-07 20:37:15 +02:00
Mitchell Hashimoto	9956e6d012	Better directory structure for plugins	2012-04-20 16:53:01 -07:00

Renamed from plugins/puppet/provisioner/puppet.rb (Browse further)