kitchen-ansible 0.0.14 → 0.0.15

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7c76809e1ae3af15a1af70c8e2a3506592a5a3fa
-  data.tar.gz: ead9e832b47e8509069250df3b4c76f073894205
+  metadata.gz: 4ac89415331c2a0fa7949888fe368bb0d18cf26e
+  data.tar.gz: c1e2f6e1e84231e1f75f30ab4f3562e6523905ad
 SHA512:
-  metadata.gz: c618628de49ae2e74afbce52a93c09b45f125174fb743e79e009d442d515899cab1ce6ebe71600a1198317a52a5fce9d62d47bc3914203a328b3f277e2e68537
-  data.tar.gz: da7d1fd5f358c495f082bef1d0c0d0f372123a97c73a69dc686bba5d8d5e499e7e04a5e747af22883eb57ea086c77fa0538246225eef03528f6bca3f63517eef
+  metadata.gz: fb9713bb088897ab10cbf0189862bf8cf30a55591aa318ff66030dfd8f746f9f4aa8df0f3bad5e55860d601aeced3c2249391b008667f1bc4412df6739c62855
+  data.tar.gz: 8876e39e61831b33cc314f9fcfd36cee3e8544774f4d2fc246d922374922d47c0fe77e190a1e1cfabba3a59358f14105d49d05c7595cb6c3e4d1e4acd9be5821

data/README.md

@@ -80,6 +80,15 @@ Create a `.kitchen.yml`, much like one the described above:
     - name: default
 ```
 
+**NOTE:** With Test-Kitchen 1.4 you not longer need chef install to run the tests. You just need ruby installed version 1.9 or higher and also add to the .kitchen.yml file
+
+```yaml
+  verifier:
+    ruby_bindir: '/usr/bin'
+```
+where /usr/bin is the location of the ruby command. 
+
+
 Then for serverspec:
     
 ```bash

data/lib/kitchen-ansible/version.rb

@@ -1,5 +1,5 @@
 module Kitchen
   module Ansible
-    VERSION = "0.0.14"
+    VERSION = "0.0.15"
   end
 end

data/lib/kitchen/provisioner/ansible_playbook.rb

@@ -643,9 +643,12 @@ module Kitchen
         end
 
         def prepare_ansible_vault_password_file
-          info('Preparing ansible vault password')
-          debug("Copying ansible vault password file from #{ansible_vault_password_file} to #{tmp_ansible_vault_password_file_path}")
-          FileUtils.cp(ansible_vault_password_file, tmp_ansible_vault_password_file_path)
+          if ansible_vault_password_file
+            info('Preparing ansible vault password')
+            debug("Copying ansible vault password file from #{ansible_vault_password_file} to #{tmp_ansible_vault_password_file_path}")
+
+            FileUtils.cp(ansible_vault_password_file, tmp_ansible_vault_password_file_path)
+          end
         end
 
         def resolve_with_librarian

data/provisioner_options.md

@@ -25,7 +25,7 @@ ansible_verbosity| 1| Sets the verbosity flag appropriately (e.g.: `1 => '-v', 2
 ansible_check| false| Sets the `--check` flag when running Ansible
 ansible_diff| false| Sets the `--diff` flag when running Ansible
 update_package_repos| true| update OS repository metadata
-chef_bootstrap_url |"https://www.getchef.com/chef/install.sh"| the chef (needed for busser to run tests)
+chef_bootstrap_url |"https://www.getchef.com/chef/install.sh"| the chef (needed for busser to run tests) NOTE: kitchen 1.4 only requires ruby to run busser so this is not required. 
 ansiblefile_path | | Path to Ansiblefile
 requirements_path | | Path to ansible-galaxy requirements
 ansible_vault_password_file| | Path of Ansible Vault Password File
@@ -34,6 +34,7 @@ ansible_vault_password_file| | Path of Ansible Vault Password File
 
 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:
 
+```yaml
     ---
     driver:
         name: vagrant
@@ -56,12 +57,22 @@ The provisioner can be configured globally or per suite, global settings act as
 
     suites:
      - name: default
+```
+
+**NOTE:** With Test-Kitchen 1.4 you not longer need chef install to run the tests. You just need ruby installed version 1.9 or higher and also add to the .kitchen.yml file
+
+```yaml
+  verifier:
+    ruby_bindir: '/usr/bin'
+```
+where /usr/bin is the location of the ruby command. 
 
 
 in this example, vagrant will download a box for ubuntu 1204 with no configuration management installed, then install the latest ansible and ansible playbook against a ansible repo from the /repository/ansible_repo directory using the defailt manifest site.yml
 
 To override a setting at the suite-level, specify the setting name under the suite's attributes:
 
+```yaml
     suites:
      - name: server
        attributes:
@@ -69,7 +80,7 @@ To override a setting at the suite-level, specify the setting name under the sui
            server_installer_url: http://downloads.app.com/v1.0
          tags:
            - server
-
+```
 
 ### Per-suite Structure
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: kitchen-ansible
 version: !ruby/object:Gem::Version
-  version: 0.0.14
+  version: 0.0.15
 platform: ruby
 authors:
 - Neill Turner
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-05-08 00:00:00.000000000 Z
+date: 2015-05-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: test-kitchen