kitchen-ansible 0.48.2 → 0.48.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 60dae088d65cb223f810daa91cb55c5f61c25e8d
4
- data.tar.gz: e171d2c56f74b2da08a75d25fce143815cf26ad9
3
+ metadata.gz: '0562836d4ca6d81634acd371268de770e2bc9040'
4
+ data.tar.gz: f42849acf33feb44db3c62f8be4eab531e941695
5
5
  SHA512:
6
- metadata.gz: 45dbb41ea30f3eff11d8dfb670baf67f3be8c2da20bd40cb2d3e19f560832effd222c64e330038119e0b24a987fb63c34ccad25ea2d833a0f0267d2f6c917f4e
7
- data.tar.gz: b522786d6078d0ac96c471667428592c9a9455642800ef08cbbff243814776754fcf392e6d41be9bc866a58eace8b1d9e575513715536c290b5bcdeb20cd0b55
6
+ metadata.gz: 5bbccf96b0fee46bcb9732788bf7be69a9b9865bac060347a11916fdfbeac232ccf85c218395c3582687bec5f230fff8aec65f11559be94c1558207c97b809f4
7
+ data.tar.gz: fdf6dd5216e34bde991ad7cd3f6635e5fefd6f89d778af3ad964be68763e4fab29a487d147510c97b3f2996b1f07ac8a1abae7be58f0dacc08777b4340509d59
@@ -1,6 +1,6 @@
1
1
  # -*- encoding: utf-8 -*-
2
2
  module Kitchen
3
3
  module Ansible
4
- VERSION = '0.48.2'.freeze
4
+ VERSION = '0.48.3'.freeze
5
5
  end
6
6
  end
@@ -46,7 +46,7 @@ module Kitchen
46
46
  default_config :ansible_yum_repo, nil
47
47
  default_config :ansible_sles_repo, 'http://download.opensuse.org/repositories/systemsmanagement/SLE_12/systemsmanagement.repo'
48
48
  default_config :python_sles_repo, 'http://download.opensuse.org/repositories/devel:/languages:/python/SLE_12/devel:languages:python.repo'
49
- default_config :chef_bootstrap_url, 'https://www.getchef.com/chef/install.sh'
49
+ default_config :chef_bootstrap_url, 'https://www.chef.io/chef/install.sh'
50
50
  # Providing we have Ruby >= 2.0 we only need Ruby. Leaving default to install Chef Omnibus for backwards compatibility.
51
51
  # Note: if using kitchen-verifer-serverspec your we can avoid needing Ruby too.
52
52
  # (Reference: https://github.com/neillturner/kitchen-ansible/issues/66 )
@@ -19,7 +19,7 @@ It installs it in the following order:
19
19
  * if require_ansible_repo is set to true (the default)
20
20
 
21
21
  Installs from the operation system repository only with the ansible version that is in the particular repository and will use the ansible_version in the package name where appropriate.
22
-
22
+
23
23
  NOTE: Set to ansible_package_name to 'ansible' when installing from the CentOS/Redhat extras repo, instead of the EPEL.
24
24
 
25
25
  # Provisioner Options
@@ -57,7 +57,7 @@ ansible_version | latest | Desired version, only affects `apt-get` installs
57
57
  ansible_yum_repo | nil | `yum` repo for EL platforms
58
58
  ansiblefile_path | | Path to Ansiblefile
59
59
  callback_plugins_path | callback_plugins | Ansible repo `callback_plugins` directory
60
- chef_bootstrap_url | `https://www.getchef.com/chef/install.sh` | The Chef install
60
+ chef_bootstrap_url | `https://www.chef.io/chef/install.sh` | The Chef install
61
61
  custom_pre_install_command | nil | Custom shell command to be used at beginning of install stage. Can be multiline.
62
62
  custom_pre_play_command | nil | Custom shell command to be used before the ansible play stage. Can be multiline. See examples below.
63
63
  custom_post_install_command | nil | Custom shell command to be used at after the install stage. Can be multiline.
@@ -104,7 +104,7 @@ update_package_repos | true | Update OS repository metadata
104
104
  wait_for_retry | 30 | number of seconds to wait before retrying converge command
105
105
  ignore_ansible_cfg | false | If true, values from ansible.cfg file will not be loaded.
106
106
 
107
- ## Ansible Inventory
107
+ ## Ansible Inventory
108
108
 
109
109
  Ansible has the concept of an [inventory](http://docs.ansible.com/ansible/latest/intro_inventory.html).
110
110
 
@@ -113,46 +113,46 @@ Ansible then connects to these servers and processes the playbook against the se
113
113
  See also [Host inventories](https://ansible-tips-and-tricks.readthedocs.io/en/latest/ansible/inventory/).
114
114
 
115
115
 
116
- ### ansible Inventory parameter
116
+ ### ansible Inventory parameter
117
117
 
118
118
  if you have an ansible inventory file you can specify it in the ansible_inventory parameter in the .kitchen.yml file.
119
119
  ```yaml
120
120
  ansible_inventory: myinventoryfile.txt
121
- ```
121
+ ```
122
122
  or if you have an ansible.cfg file specify
123
123
  ```yaml
124
- ansible_inventory: none
125
- ```
126
- it will look for the file in the root of your repository.
124
+ ansible_inventory: none
125
+ ```
126
+ it will look for the file in the root of your repository.
127
127
 
128
- or it can be a directory from the root of your repository and contain scripts to implement [dynamic inventory](http://docs.ansible.com/ansible/latest/intro_dynamic_inventory.html)
128
+ or it can be a directory from the root of your repository and contain scripts to implement [dynamic inventory](http://docs.ansible.com/ansible/latest/intro_dynamic_inventory.html)
129
129
 
130
130
  ### hosts parameter
131
131
 
132
- if you don't specify an inventory file then you must specify the hosts parameter in the .kitchen.yml file.
132
+ if you don't specify an inventory file then you must specify the hosts parameter in the .kitchen.yml file.
133
+
134
+ kitchen ansible uses this information to create a hosts file that is used by ansible with the ansible command is run.
133
135
 
134
- kitchen ansible uses this information to create a hosts file that is used by ansible with the ansible command is run.
135
-
136
136
  it can either be a name of a single server
137
137
 
138
138
  ```yaml
139
- hosts: myhost
139
+ hosts: myhost
140
140
  ```
141
141
 
142
- or any array of hosts:
142
+ or any array of hosts:
143
143
 
144
144
  ```yaml
145
- hosts:
145
+ hosts:
146
146
  - myhost1
147
147
  - myhost2
148
- ```
148
+ ```
149
149
 
150
- the hosts file that is generated always contains in the first line
150
+ the hosts file that is generated always contains in the first line
151
151
 
152
152
  ```yaml
153
153
  localhost ansible_connection=local
154
154
  ```
155
- so that it will process against the locahost.
155
+ so that it will process against the locahost.
156
156
 
157
157
  and it will create a hosts file that includes the hosts you specify
158
158
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: kitchen-ansible
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.48.2
4
+ version: 0.48.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Neill Turner
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-04-07 00:00:00.000000000 Z
11
+ date: 2018-04-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rspec