kitchen-puppet 0.0.14 → 0.0.15

data/provisioner_options.md

@@ -1,5 +1,5 @@
 
-# Provisioner Options
+# Puppet Apply Provisioner Options
 
 key | default value | Notes
 ----|---------------|--------
@@ -31,8 +31,9 @@ require_chef_for_busser | true | Install chef as currently needed by busser to r
 resolve_with_librarian_puppet | true | Use librarian_puppet to resolve modules if a Puppetfile is found 
 puppet_config_path | | path of custom puppet.conf file 
 puppet_environment | nil | puppet environment for running puppet apply 
+remove_puppet_repo | false | remove copy of puppet repository on server after running puppet
 
-## Configuring Provisioner Options
+## Puppet Apply Configuring Provisioner Options
 
 The provisioner can be configured globally or per suite, global settings act as defaults for all suites, you can then customise per suite, for example:
 
@@ -79,3 +80,77 @@ It can be beneficial to keep different Puppet layouts for different suites. Rath
 When specifying a puppet version, you must use this format: "3.6.2-1puppetlabs1". I have
 no idea why Puppet versioned their repository with a trailing
 "-1puppetlabs1", but there it is. 
+
+
+# Puppet Agent Provisioner Options
+
+key | default value | Notes
+----|---------------|--------
+puppet_version | "latest"| desired version, affects apt installs.
+puppet_platform | naively tries to determine | OS platform of server
+require_puppet_repo | true | Set if using a puppet install from yum or apt repo
+puppet_apt_repo | "http://apt.puppetlabs.com/puppetlabs-release-precise.deb"| apt repo
+puppet_yum_repo | "https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm"| yum repo
+require_puppet_omnibus | false | Set if using omnibus puppet install
+puppet_omnibus_url | | omnibus puppet install location.
+puppet_omnibus_remote_path | "/opt/puppet" | Server Installation location of an omnibus puppet install.
+puppet_detailed_exitcodes | nil | Provide transaction information via exit codes.
+puppet_logdest | nil | Where to send messages. Choose between syslog, the console, and a log file.
+puppet_masterport | nil | The port on which to contact the puppet master. 
+puppet_test | false | Enable the most common options used for testing.
+puppet_onetime | true | Run the configuration once.
+puppet_no_daemonize | true | Do not send the process into the background. 
+puppet_server | nil | will default to 'puppet'. Useful for interactively running when used with the --no-daemonize option. 
+puppet_waitforcert | '0' | Time to wait for certificate if agent does not yet have certificates  
+puppet_certname | nil | Set the certname (unique ID) of the client
+puppet_digest | nil | Change the certificate fingerprinting digest algorithm. The default is SHA256 
+puppet_debug| false| Enable full debugging logging on puppet run
+puppet_verbose| false| Extra information logging on puppet run
+puppet_noop| false| puppet runs in a no-op or dry-run mode
+update_package_repos| true| update OS repository metadata
+custom_facts| Hash.new | Hash to set the puppet facts before running puppet apply
+chef_bootstrap_url |"https://www.getchef.com/chef/install.sh"| the chef (needed for busser to run tests)
+puppet_agent_command | nil | Overwrite the puppet agent command. Needs "sudo -E puppet agent" as a prefix. 
+require_chef_for_busser | true | Install chef as currently needed by busser to run tests 
+puppet_config_path | | path of custom puppet.conf file 
+
+
+## Puppet Agent Configuring Provisioner Options
+
+The provisioner can be configured globally or per suite, global settings act as defaults for all suites, you can then customise per suite, for example:
+
+    ---
+    driver:
+      name: vagrant
+
+    provisioner:
+      name: puppet_agent
+      puppet_debug: true
+      puppet_verbose: true
+      puppet_server:  puppetmaster-nocm-ubuntu-1204
+      
+    platforms:
+    - name: nocm_ubuntu-12.04
+      driver_plugin: vagrant
+      driver_config:
+        box: nocm_ubuntu-12.04
+        box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
+
+    suites:
+     - name: default
+
+
+In this example, vagrant will download a box for ubuntu 1204 with no configuration management installed, then install the latest puppet and run puppet agent against a puppet master at puppetmaster-nocm-ubuntu-1204
+
+NOTE: It is important that the server can resolve the hostname ip address of the puppetmaster, in this case puppetmaster-nocm-ubuntu-1204
+and the puppetmaster must be able to resolve the hostname ip address address of the hostname of the node running puppet agent. 
+This can be done by settings in the /etc/hosts files before running puppet. 
+
+NOTE: For testing it is possible to set the puppetmaster to autosign the certificate of a node by created a file /etc/puppet/autosign.conf that contains an *.
+
+
+To override a setting at the suite-level, specify the setting name under the suite:
+
+    suites:
+     - name: default
+       manifest: foobar.pp

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kitchen-puppet
 version: !ruby/object:Gem::Version
-  version: 0.0.14
+  version: 0.0.15
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-10-03 00:00:00.000000000 Z
+date: 2014-10-10 00:00:00.000000000 Z
 dependencies: []
 description: ! '== DESCRIPTION:
 
@@ -34,6 +34,7 @@ files:
 - kitchen-puppet.gemspec
 - lib/kitchen-puppet/version.rb
 - lib/kitchen/provisioner/puppet/librarian.rb
+- lib/kitchen/provisioner/puppet_agent.rb
 - lib/kitchen/provisioner/puppet_apply.rb
 - lib/kitchen/provisioner/puppet_apply_spec.rb
 - provisioner_options.md