Commit Graph

1700 Commits

Author SHA1 Message Date
Seth Vargo e7b25f1bee
Update CHANGELOG 2016-06-16 15:32:51 -04:00
Seth Vargo 9dc6e190e9
Update CHANGELOG 2016-06-16 15:23:21 -04:00
Seth Vargo e65f61605d
Update CHANGELOG 2016-06-15 12:20:23 +02:00
Seth Vargo 172e76abe9
Bump version for development 2016-06-13 23:35:28 +02:00
Seth Vargo bedaeee190
Version bump v1.8.4 2016-06-13 10:21:40 +02:00
Seth Vargo 349d320984
Update CHANGELOG 2016-06-12 16:23:59 +02:00
Gilles Cornu 008ebb5afd Update CHANGELOG
[ci skip]
2016-06-11 07:37:38 +02:00
Seth Vargo 2cecbfd2eb
Update CHANGELOG 2016-06-11 02:37:09 +02:00
Mitchell Hashimoto 3ba52d0a37
up version for dev 2016-06-10 11:13:01 -07:00
Mitchell Hashimoto 018cbc6550
v1.8.3 2016-06-10 09:43:11 -07:00
Gilles Cornu 14c997317a Update CHANGELOG [GH-6526, GH-7190]
[ci skip]
2016-06-09 14:58:48 +02:00
Gilles Cornu bb9dba56ac provisioners/ansible_local: add "pip" install_mode
These changes have been validated against the following guest systems:
- Debian 7 and 8
- Ubuntu 12.04, 14.04 and 16.04
- Fedora 21 and 23
- CentOS 7
- OracleLinux 7
- Scientific Linux 7

At the moment, the pip setup (via get-pip.py script) is not working for
RHEL6-like systems (CentOS 6.6, OracleLinux 6.5, Scientific Linux 6),
because Python 2.6 has been deprecated and is no longer supported by
Python core team. I consider this limitation with low priority in
Vagrant context.

The `:pip` install_mode is currently not implemented for the following
platforms:
- OpenSUSE
- ArchLinux
- FreeBSD

Known Issue: By using get-pip.py script, any previous pip installation
will be most probably overrided. This could be an issue for Python
developers who would prefer to keep their base box setup untouched. In
future iteration, it could be possible to choose to reinstall/upgrade
pip or not. issue for Python developers who would prefer to keep their
base box setup untouched. In future iteration, it could be possible to
choose to reinstall/upgrade pip or not.

Resolve GH-6654

Resolve GH-7167 as the `version` option is now considered to select the
version of Ansible to be installed.
2016-06-08 23:53:58 +02:00
Seth Vargo 3443eaa05f
Update CHANGELOG 2016-06-06 19:38:02 -04:00
Seth Vargo 6c86045cd9
Update CHANGELOG 2016-06-06 19:29:41 -04:00
Seth Vargo 562180c75c
Update CHANGELOG 2016-06-06 19:14:41 -04:00
Seth Vargo a21e154efd
Update CHANGELOG 2016-06-06 18:42:22 -04:00
Seth Vargo e9ccc0a357
Update CHANGELOG 2016-06-06 18:27:19 -04:00
Seth Vargo 4ec2b2af85
Update CHANGELOG 2016-06-06 15:47:07 -04:00
Seth Vargo 8d2ca8a1eb
Update CHANGELOG 2016-06-04 15:22:49 -04:00
Gilles Cornu a7ee56459b provisioners/ansible(both): fix ansible config files presence checks
With this change, the presence of Ansible configuration files (like
playbook file, inventory path, galaxy role file, etc.) is no longer
performed by the `config` classes, but by the `provisioner` classes
(at the beginning of the provision command).

This change fixes several issues:

- Resolve #6984 as `provision` method are only executed when remote
  (ssh) communication with the guest machine is possible.
- Resolve #6763 in a better way than 4e451c6 initially did.
- Improve the general provisioner speed since the `config` checks are
  actually triggered by many vagrant actions (e.g. `destroy`,...), and
  can also be triggered multiple times during a vagrant run (e.g. on
  callback request made by the machine provider).

Unlike the former `config`-based checks, the provision action won't
collect all the invalid options, but only report the first invalid
option found and abort the execution.

Some unit tests were not implemented yet to save my scarce "open source
contribution time" for other important issues, but they should be done
at last via GH-6633.
2016-06-01 06:40:23 +02:00
Seth Vargo 37cdabc2e7
Update CHANGELOG 2016-05-31 20:10:16 -04:00
Seth Vargo 9a28a03b2c
Update CHANGELOG 2016-05-31 17:56:40 -04:00
Seth Vargo 9c5404c9b8
Update CHANGELOG 2016-05-30 21:02:09 -04:00
Seth Vargo ef2ddcec26
Update CHANGELOG 2016-05-30 17:28:11 -04:00
Seth Vargo 4236ddc021
Update CHANGELOG 2016-05-30 15:38:37 -04:00
Seth Vargo f7ffec3589
Update CHANGELOG 2016-05-29 18:48:21 -04:00
Seth Vargo 791ad7ac8e
Update CHANGELOG 2016-05-29 14:48:56 -04:00
Seth Vargo 131c8c811e
Update CHANGELOG 2016-05-29 01:20:56 -04:00
Seth Vargo 7713a52f01
Update CHANGELOG 2016-05-29 01:11:53 -04:00
Seth Vargo 71dad1d7a4
Update CHANGELOG 2016-05-29 00:59:04 -04:00
Seth Vargo 2f3973ef69
Update CHANGELOG 2016-05-29 00:56:47 -04:00
Seth Vargo d9a9a7dd1b
Update CHANGELOG 2016-05-29 00:47:37 -04:00
Seth Vargo 453fdb02d0
Update CHANGELOG 2016-05-28 17:11:32 -04:00
Seth Vargo 61f4128003
Update CHANGELOG 2016-05-27 19:09:38 -04:00
Seth Vargo 4250fb5514
Update CHANGELOG 2016-05-27 19:03:23 -04:00
Seth Vargo 9baa5baff6
Update CHANGELOG 2016-05-27 18:39:23 -04:00
Seth Vargo ef22149e9c
Update CHANGELOG 2016-05-27 17:39:06 -04:00
Seth Vargo a4803c0869
Update CHANGELOG 2016-05-27 17:17:29 -04:00
Seth Vargo a92d841e2a
Update CHANGELOG 2016-05-27 17:08:46 -04:00
Seth Vargo a735608787
Update CHANGELOG 2016-05-27 16:06:56 -04:00
Seth Vargo ee492629ac
Update CHANGELOG 2016-05-20 10:46:49 -04:00
Seth Vargo 1571879a4b
Update CHANGELOG 2016-05-19 11:34:50 -04:00
Seth Vargo f6db93d4be
Update CHANGELOG 2016-05-16 12:07:41 -04:00
Gilles Cornu cf908d35e0 provisioners/ansible_local: Run galaxy from `provisioning_path` directory
Since it is now possible to specify some Galaxy settings in an
`ansible.cfg` file, it makes sense to run `ansible-galaxy` from the
same working directory as `ansible-playbook` execution does.

See http://docs.ansible.com/ansible/intro_configuration.html#galaxy-settings
2016-04-24 00:26:59 +02:00
Gilles Cornu 327392d0fb Fix a CHANGELOG entry
[ci skip]
2016-04-21 00:37:31 +02:00
Gilles Cornu afb9af1549 Update CHANGELOG
[ci skip]
2016-04-21 00:34:19 +02:00
Seth Vargo 2c553290b8
Update CHANGELOG 2016-04-17 23:15:31 +05:30
Seth Vargo bfac44aded Update CHANGELOG 2016-04-08 10:22:54 -04:00
Seth Vargo 9c0a4bb562 Update CHANGELOG 2016-04-05 10:46:48 -04:00
Seth Vargo be9a88d2a0 Update CHANGELOG 2016-04-05 10:42:58 -04:00