haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
vagrant/website
History
Gilles Cornu 8834afbd8e
provisioners/ansible(both): Add compatibility mode 
With this change, it is now possible to get rid of many deprecation
messages successively introduced in Ansible 1.9, and 2.0. More
interesting, the generated inventory will contain the recommended
variable names (e.g. `ansible_host` instead of `ansible_ssh_host`)
when the compatibility mode is set to '2.0'.

Details:

- Add `compatibility_mode` option to control the Ansible parameters
  format to be used. The value corresponds to the minimal version
  supported. For the moment, possible values are '1.8' (corresponding to
  Vagrant's former behaviour) or '2.0'.
  Note that a dynamic inventory generated in compatibility mode '2.0'
  is not supported by Ansible 1.x. On the other hand, Ansible 2.x so far
  supports inventory format generated by the compatibility mode '1.8'.

- Add compatibility mode auto-detection, based on the available Ansible
  version. This is the default behaviour in order to bring a maximum of
  user friendliness. The drawback of this approach is to let potential
  compatibility breaking risks, for `ansible` provisioner setups that
  already integrate Ansible 2.x **AND** rely on the existence of
  the generated `_ssh` variable names. Thanks to the vagrant warnings
  (and its release notes), I argue that it is worth to offer
  auto-detection by default, which offers a sweet transition to most
  users.

- Add `become`, `become_user` and `ask_become_pass` options and their
  backwards compatible aliases. The legacy options are now deprecated.

Note that we intentionally didn't provide a '1.9' compatibility mode,
as it would add extra-complexity for practically no added-value.
To my knowledge, the Ansible 2.x series haven't introduced yet any major
changes or deprecations that would motivate to introduce a higher
version compatibility mode (to be confirmed/verified).

Resolve GH-6570

Still Pending:

- Optimization: Reduce the number of `ansible` command executions.
  Currently two exec calls will be performed when the compatibility
  mode auto-detection is enabled (i.e. by default). We could make the
  provisioner a little bit smarter to only execute `ansible` only once
  in any situation (by combining "presence" and "version" checks).

- User-friendliness: Add better validator on `compatibility_mode`
  option, and shows a warning or an error instead of the silent
  fallback on the auto-detection modus.

- Test coverage: All the added behaviours are not fully covered yet.
 		2017-09-06 17:12:22 +02:00
..
scripts Update deploy process 2017-08-02 14:13:58 -04:00
source provisioners/ansible(both): Add compatibility mode 2017-09-06 17:12:22 +02:00
Gemfile Update middleman-hashicorp to 0.3.28 for mega nav fixes 2017-06-26 16:18:42 -04:00
Gemfile.lock Update middleman-hashicorp to 0.3.28 for mega nav fixes 2017-06-26 16:18:42 -04:00
LICENSE.md Update license 2017-03-08 11:39:24 -08:00
Makefile Update middleman-hashicorp to 0.3.28 for mega nav fixes 2017-06-26 16:18:42 -04:00
README.md Update website 2017-03-08 11:32:17 -08:00
config.rb Update vagrant website version to 1.9.8 2017-08-23 12:11:24 -07:00
packer.json Update deploy process 2017-08-02 14:13:58 -04:00
redirects.txt Update deploy process 2017-08-02 14:13:58 -04:00

README.md

Vagrant Website

This subdirectory contains the entire source for the Vagrant Website. This is a Middleman project, which builds a static site from these source files.

Contributions Welcome!

If you find a typo or you feel like you can improve the HTML, CSS, or JavaScript, we welcome contributions. Feel free to open issues or pull requests like any normal GitHub project, and we'll merge it in.

Running the Site Locally

Running the site locally is simple. Clone this repo and run make website.

Then open up http://localhost:4567. Note that some URLs you may need to append ".html" to make them work (in the navigation).