850716b220
provisioners/ansible: remove erroneous comment
...
[ci skip]
2015-12-07 22:28:23 +01:00
c60a71861f
Update CHANGELOG
2015-12-07 10:58:46 -05:00
36b87bb32b
Merge pull request #6650 from mitchellh/sethvargo/checksum_case
...
Ignore case when comparing checksums
2015-12-07 10:57:29 -05:00
5c09e94f1a
Clarify that support might be in a later Vagrant version
2015-12-07 10:57:26 -05:00
4e21dd78e4
Ignore case when comparing checksums
...
Fixes GH-6648
2015-12-07 10:30:46 -05:00
9f3ebef810
Support ansible install on RedHat derivates and Fedora.
...
Fixes #6636
2015-12-07 15:44:20 +01:00
44eac3c819
Merge pull request #6643 from mkuzmin/util-powershell
...
Fix `uninitialized constant` error in `vagrant powershell` command
2015-12-05 12:24:33 -05:00
546649fb9e
Fix `uninitialized constant` error in `vagrant powershell` command
2015-12-05 17:24:58 +03:00
c20e1bb594
provisioners/ansible: support host pattern ranges
...
Introduction of "unsafe" numeric or alphabetic patterns in the generated inventory
Close #3539
2015-12-05 07:11:27 +01:00
3a793a2721
provisioners/ansible(both): minor tweak in en.yml
...
Related to #3539 .
2015-12-05 07:10:11 +01:00
c901e81e37
docs (ansible): update and fixes for [GH-3539]
...
- clearly mention that this feature is available since Vagrant 1.8.0
- reorganize the special notes
- update the examples to be more focused, and mention that a host range
is not coherent with `Vagrantfile` machine definitions.
2015-12-05 06:59:29 +01:00
b7e9437a77
#3539 - Fixed syntax, language and logic according to comments made by reviewer in PR #6639
2015-12-04 10:05:07 +01:00
f5f568b66b
Added plain Symbol group name for unit test
2015-12-04 02:16:01 +01:00
5cbbbb5e28
#3539 - Can't use alphanumeric patterns for box names in ansible.groups: Changed iteration logic for warning message and fixed regex typo
2015-12-04 01:29:22 +01:00
af6a80472e
#3539 - Can't use alphanumeric patterns for box names in ansible.groups: added unit test for host range patterns
2015-12-04 01:26:04 +01:00
934bcf9419
#3539 - Can't use alphanumeric patterns for box names in ansible.groups: Host Range Pattern Regex, notification and updates to provisioning web source
2015-12-04 01:13:59 +01:00
dde7f4697f
Merge branch 'gildegoma/review-6626'
...
Related to #6619 , #6626 and #6627
2015-12-03 21:52:34 +01:00
cc2d11b497
provisioners/ansible+ansible_local: inventory vars
...
Add support for group and host variables in the generated inventory.
Close #6619
2015-12-03 21:50:53 +01:00
8517014a99
provisioners/ansible: update inventory groups tests
...
With the introduction of inventory variables, group members provided as
String are not splitted (by ' ') into an array (instead of
auto-conversion to a single-item array).
2015-12-03 09:39:12 +01:00
4c137a9b6b
provisioners/ansible: fix comment indentation
...
[ci skip]
2015-12-03 09:36:57 +01:00
9867281971
provisioners/ansible: allow symbol in `groups` key
...
After c49a146467
2015-12-03 09:34:53 +01:00
06e772a241
docs (ansible): update inventory host vars example
...
Better reflect the true generated inventory output.
[ci skip]
2015-12-03 08:14:47 +01:00
7caaffbf38
website/docs: update machine readable output options
2015-12-02 18:07:00 -08:00
30d9e243bb
fix failing tests
2015-12-02 18:03:08 -08:00
350da6e1d5
commands/ssh_config: output machine readable output
2015-12-02 17:53:08 -08:00
5c4e71e317
core: machine output provider info for the machine
2015-12-02 13:06:07 -08:00
cee517d963
core: fix machine readable UI to contain target and have proper format
2015-12-02 13:06:07 -08:00
c99de13893
ansible docs: inventory variables support in 1.8+
...
Ref #6619
2015-12-02 08:47:58 +01:00
3dbcf5083c
provisioners/ansible(both) add more unit tests
...
Improve the test coverage of 'get_inventory_host_vars_string' method.
2015-12-02 08:42:44 +01:00
c49a146467
provisioners/ansible(both): alias String-to-Symbol
...
String and Symbol types are different when used as a Hash key. By
default the Vagrant machine names are set in Symbol format, but users
may write their `host_vars` entries with String keys. This is a very
simple way to ensure smooth experience, without having to coerce the
data types during the config validation (e.g. with a library like
Hashie, which is currently not in the Vagrant dependencies)
See also:
- https://bugs.ruby-lang.org/issues/5964#note-17
- https://github.com/intridea/hashie#keyconversion
2015-12-02 08:37:41 +01:00
77b11a989c
Implemented host_vars option.
2015-12-01 18:56:28 +01:00
a5dd61c450
Added test to expect host vars being inserted into inventory.
2015-12-01 18:56:28 +01:00
78766ded4e
Document host_vars option.
2015-12-01 18:56:28 +01:00
dd4ae1a51c
Parse and insert group variables into the generated inventory.
2015-12-01 18:56:28 +01:00
3fbbfeb862
Expect group variables to be inserted in the test.
2015-12-01 18:56:28 +01:00
a5ff241586
Updated documentation to reflect the possibility of adding group vars.
2015-12-01 16:43:57 +01:00
7d81728e45
Add checksum validation for the VirtualBox installs on Windows and OS X
...
Use Vagrant::Util::FileChecksum to validate the downloaded VirtualBox
installers.
SHA-256 checksums for VirtualBox files are available at
https://www.virtualbox.org/download/hashes/5.0.10/SHA256SUMS .
Fixes #6611 .
2015-11-28 00:04:41 -08:00
a87dec60ad
Merge pull request #6606 from rubenv/patch-1
...
Document missing sudoers item
2015-11-27 19:31:46 -05:00
652b4dac55
Vagrant Issue #6608
...
Refactor and repair regular expression attempting to match present interfaces.
The refactored regular expression will match on enp* ens* eth* variants.
2015-11-27 13:13:44 -08:00
3c1c553789
Document missing sudoers item
2015-11-27 09:49:38 +01:00
64ff69c64b
Only run cleanup tasks when they are defined on the provisioner
...
This helps with some confusion caused in GH-2538, since the output says:
> Running cleanup tasks for 'shell' provisioner...
But that's actually not true. It is running the cleanup tasks iff the
provisioner defined a cleanup task. This commit changes the
provisioner_cleanup middleware to only run cleanup tasks if the subclass
defines a cleanup task.
The reason we can't just check if the provisioner `respond_to?` the
`cleanup` method is because the parent provisioner base class (which
all provisioners inherit from) defines a blank cleanup method. This is
important because it means we never risk calling an unimplemented
cleanup function, and it also helps define the public API for a
provisioner.
2015-11-26 13:11:51 -05:00
b63fdf756f
Merge pull request #6601 from romulodl/update_provision_with_help_message
...
update help message on --provision-with to add by provisioner name
2015-11-26 12:23:36 -05:00
2f2c442457
Document that the `shutdown` command must be on the $PATH
...
- Fixes GH-6449
- Closes GH-6450
2015-11-26 12:22:23 -05:00
a9e1ef4fe3
update help message on --provision-with to add by provisioner name
2015-11-26 15:17:09 +00:00
32bb316564
Update CHANGELOG.md
...
close #5086
2015-11-25 22:48:56 +01:00
eaf918ec35
Merge branch 'gildegoma/5086-ansible-winrm' into master
2015-11-25 22:46:08 +01:00
2221a1dc8f
Merge pull request #6599 from legal90/test-linked-clone
...
Add acceptance test for linked clones
2015-11-25 15:41:22 -05:00
6c40a8b66c
Update CHANGELOG
2015-11-25 15:40:54 -05:00
c24a44a7c6
Merge pull request #6591 from mitchellh/sethvargo/ports
...
Add `vagrant port` command
2015-11-25 15:39:59 -05:00
3d4a133dce
Add acceptance test for linked clones
2015-11-25 00:23:19 +02:00
Gilles Cornu
Seth Vargo
Rickard von Essen
Michael Kuzmin
Kamjar Gerami
Mitchell Hashimoto
Christian Henz
Reed Loden
Joshua Harshman
Ruben Vermeersch
Romulo De Lazzari
Mikhail Zholobov