kitchen-ansiblepush 0.10.1 → 0.11.0

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
- SHA1:
3
- metadata.gz: 4cddf05fc2cac0808c450d5a3e279268870e869e
4
- data.tar.gz: b40f2372c447f9fda2ad2c12f87a07e615dcfa68
2
+ SHA256:
3
+ metadata.gz: b23b040db1827ecb2b42a524b6fa05f5ce870ef8e2ddb858bf7112ba51c305d8
4
+ data.tar.gz: f328cb4cf4a8a4a0b92aa587e1441a93906eb1da3f546413a4f63b38e733d2d7
5
5
  SHA512:
6
- metadata.gz: 93354ede800e70c0cae24e42bb2c63fe9f6b052acc70643a16925bd04f955f87548ab37e0b7b275f719791fb5c7ad4679d267bb25c37e4bc7919fb828d792321
7
- data.tar.gz: ccf14a905847beabfa73e2785e5b45b227de02acfecede71211588ec096a2baa96221b0adeee9fbab13cc21a361432132f9e45668b2c5ba51e5f0967626ca685
6
+ metadata.gz: 92e816f149f19692ac9679a0c8166af59065ac25092c5b6eec4f080cb6fe0b18e9e35a42aa2d93195236ab3d9d83223ac363c5ead45c43df9d4eba0a4061884a
7
+ data.tar.gz: e0ff570800f085e060da6999cd5386e57abbd2b54a8a2fd384b30b1e306ea7365998fc53367d9aced467768567503db857f474b9face96c191274b56ae8f2f2f
data/README.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # kitchen-ansiblepush
2
2
  [![Gem Version](https://badge.fury.io/rb/kitchen-ansiblepush.svg)](https://badge.fury.io/rb/kitchen-ansiblepush)
3
3
  [![Gem Downloads](http://ruby-gem-downloads-badge.herokuapp.com/kitchen-ansiblepush?type=total&color=brightgreen)](https://rubygems.org/gems/kitchen-ansiblepush)
4
- [![Build Status](https://travis-ci.org/ahelal/kitchen-ansiblepush.svg?branch=master)](https://travis-ci.org/ahelal/kitchen-ansiblepush)
4
+ ![Ruby](https://github.com/ahelal/kitchen-ansiblepush/workflows/Ruby/badge.svg?branch=master)
5
5
 
6
6
  A test-kitchen plugin that adds the support for ansible in push mode i.e. normal mode :)
7
7
 
@@ -73,7 +73,7 @@ provisioner :
73
73
  pass_transport_password: false
74
74
  ## (optional), if you want to set specific environment variables when running ansible
75
75
  environment_vars:
76
- PROXMOX_URL: https://example.com:8006
76
+ PROXMOX_URL: https://example.com:8006
77
77
  ```
78
78
  ## Idempotency test
79
79
  If you want to check your code is idempotent you can use the idempotency_test. Essentially, this will run Ansible twice and check nothing changed in the second run. If something changed it will list the tasks. Note: If your using Ansible callback in your config this might conflict.
@@ -1,6 +1,7 @@
1
1
  #!/usr/bin/env ruby
2
+ # frozen_string_literal: true
2
3
 
3
- require 'kitchen-ansible/print_inventory_cli.rb'
4
+ require 'kitchen-ansible/print_inventory_cli'
4
5
 
5
6
  print_inventory = PrintInventory.new
6
7
  print_inventory.run
@@ -30,6 +30,8 @@ def generate_instance_inventory(name, host, mygroup, instance_connection_option,
30
30
  temp_hash['ansible_winrm_server_cert_validation'] = 'ignore'
31
31
  temp_hash['ansible_winrm_transport'] = 'ssl'
32
32
  temp_hash['ansible_connection'] = 'winrm'
33
+ temp_hash['ansible_host'] = temp_hash['ansible_ssh_host']
34
+ temp_hash['ansible_user'] = temp_hash['ansible_ssh_user']
33
35
  end
34
36
  { name => temp_hash }
35
37
  end
@@ -1,5 +1,5 @@
1
1
  module Kitchen
2
2
  module AnsiblePush
3
- VERSION = '0.10.1'.freeze
3
+ VERSION = '0.11.0'.freeze
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: kitchen-ansiblepush
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.10.1
4
+ version: 0.11.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Adham Helal
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2019-04-21 00:00:00.000000000 Z
11
+ date: 2022-09-14 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: test-kitchen
@@ -69,8 +69,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
69
69
  - !ruby/object:Gem::Version
70
70
  version: '0'
71
71
  requirements: []
72
- rubyforge_project: "[none]"
73
- rubygems_version: 2.5.2.3
72
+ rubygems_version: 3.0.3.1
74
73
  signing_key:
75
74
  specification_version: 4
76
75
  summary: ansible provisioner for test-kitchen