Re: [vagrant-up] proposal for winrm connection, presigned insecure cert

Hey there, Thank you Pixel Fairy for reporting this improvement request. Thank you Alvaro and Mário for your useful inputs. Ansible support for Windows has without any doubt strongly evolved since late 2015, which is the time when the WinRM support was added to the Ansible provisioner in

[vagrant-up] Re: Vagrant GitHub Repositories

Congratulations!! That looks cool, but I think it will be even nicer if the vagrant repository could be pinned on https://github.com/hashicorp ;-) Best, Gilles Le jeudi 14 septembre 2017 23:51:48 UTC+2, Chris Roberts a écrit : > > Hi everyone, > > I am happy to announce that the Vagrant code

[vagrant-up] Ansible Provisioners will soon support Ansible 2.x compatibility mode

in response to this mailing-list post (and not in the PR, which discussion thread is reserved for the code review). Many thanks in advance for your help on this! Best regards, Gilles Cornu -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-gui

[vagrant-up] Re: Vagrant supporting Ansible -u command

Hi Ian, Excellent News! Best regards, Gilles Le mercredi 12 octobre 2016 10:13:16 UTC+2, Ian Smith a écrit : > > Hi Gilles, > > Sorry error between chair and keyboard this time. Now that the override > file is being read there was an ansible_ssh_host line in the override file > which overrode

[vagrant-up] Re: Problem passsing raw arguments to Ansible provisioner

Hi, Sorry for responding/reviving this thread so late. This is indeed a known issue, that is still present in latest versions of Vagrant (1.8.x). I created https://github.com/mitchellh/vagrant/issues/7890 to track its resolution. Best, Gilles Le jeudi 20 mars 2014 05:34:51 UTC+1, Ben Turner a

[vagrant-up] Re: Vagrant supporting Ansible -u command

vision "demo", type: "ansible" do |ansible| >> ansible.verbose = "v" >> ansible.playbook = "demo.yml" >> ansible.raw_arguments = ["-e '@overridden_variables.json'", "-u >> ansible_user"] >> re

[vagrant-up] Re: Vagrant supporting Ansible -u command

Hi Ian, As of Vagrant 1.8+ the Ansible remote user is forced by default. Therefore your use case requires to set the "force_remote_user" option to *false*. See: - https://www.vagrantup.com/docs/provisioning/ansible.html#force_remote_user -

[vagrant-up] Unwanted debug informations

Hi Debo, Please check that the ´verbose´ option of the ansible provisioner is unset (or set to ´false´). I suppose it's not the case on the chattier machine. Otherwise, do you use the VAGRANT_LOG environment variable? Cheers, Gilles -- You received this message because you are subscribed to

[vagrant-up] Unwanted debug informations

Gotcha, now I rembember of this bug. I fixed it in https://github.com/mitchellh/vagrant/blob/gildegoma/2103-ansible-local/plugins/provisioners/ansible/provisioner/base.rb But missed to port it to master branch . I'll fix it for 1.7.3, thanks for reporting it. Note are you sûre that the less

[vagrant-up] Re: Ansible provisioner: how to include the ansible_ssh_private_key_file in the generated inventory?

Hey Eric, Thanks for your questions! vagrant sets different private keys for each hosts This is a new feature introduced in Vagrant 1.7.0, that you can easily disable by adding this setting in your Vagrantfile: config.ssh.insert_key = false Another possible workaround (if you really want to

Re: [vagrant-up] Feature Idea: Add more global commands

:25 AM, Gilles Cornu gilles.co...@gmail.com wrote: After the introduction of command global-status https://docs.vagrantup.com/v2/cli/global-status.html, I personally feel frustrated to not be able to run commands like (from any filesystem location): - vagrant global-halt - vagrant

[vagrant-up] Feature Idea: Add more global commands

After the introduction of command global-status https://docs.vagrantup.com/v2/cli/global-status.html, I personally feel frustrated to not be able to run commands like (from any filesystem location): - vagrant global-halt - vagrant global-suspend - vagrant global-destroy Another

Re: [vagrant-up] Ansible Provisioning fails as ssh cannot connect

with ansible 1.8.1 and symlinks. Things are working fine after upgrading to 1.8.2, which I just did(after uploading test results to pastebin). Thank you everyone for the help. On Fri, Dec 12, 2014 at 8:10 PM, Gilles Cornu gilles.co...@gmail.com wrote: Mehul, That's weird... but at least you're

Re: [vagrant-up] Ansible Provisioning fails as ssh cannot connect

Mehul, You perfectly understood, the Vagrant Ansible provisioner is host-based (a guest-based provisioner for ansible is planned, but not availabled yet, see https://github.com/mitchellh/vagrant/issues/2103) You are using auto-generated inventory as expected, and your failure looks quite

Re: [vagrant-up] Ansible Provisioning fails as ssh cannot connect

décembre 2014 14:47:05 UTC+1, Gilles Cornu a écrit : Mehul, You perfectly understood, the Vagrant Ansible provisioner is host-based (a guest-based provisioner for ansible is planned, but not availabled yet, see https://github.com/mitchellh/vagrant/issues/2103) You are using auto-generated

Re: [vagrant-up] Ansible Provisioning fails as ssh cannot connect

Mehul, That's weird... but at least you're now able to demonstrate that the problem can be reproduced without Vagrant, and that the problem is either in Ansible code or in your Ansible configuration/integration. Just to be 100% sure, that both cases (vagrant provision versus shell

[vagrant-up] Re: Vagrant can't run ansible when provisioning

Mike, I'll try to help you via StackOverflow thread. Best regards, Gilles Le jeudi 27 novembre 2014 17:36:27 UTC+1, Mike Thirlwell a écrit : Also posted on Stack Overflow: http://stackoverflow.com/questions/27174405/vagrant-cant-run-ansible-when-provisioning I have created a Vagrantfile to

[vagrant-up] Re: Ansible provisioner: ask_vault_pass and vault_password_file do not function

Hi Lars, Thanks for putting relevant information (like installed versions) in your questions. The ask_vault_pass and vault_password_file options were added in Vagrant 1.6.0 (see GH-3338 https://github.com/mitchellh/vagrant/pull/3338). An upgrade is thus needed (otherwise you can always use

[vagrant-up] Re: Does Vagrant require a separate installation of Ansible?

Hello Julien, Ansible is not installed by Vagrant. See http://docs.ansible.com/intro_installation.html for more details about how to install Ansible (note that only Unix operating systems are supported). If you want to avoid installing Ansible on Vagrant's host (or if your users are based on

[vagrant-up] Re: using a different username for provisioning

Hi, Note: I try to post my answer a third time, but I am suffering from a very annoying anti-spam filter problem (the two deleted messages are mine, mitchellh is aware of that problem, sorry for the noise) *I'm asking for the `vagrant` user to not be created and instead a user account with a

Re: [vagrant-up] using a different username for provisioning

I'm asking for the `vagrant` user to not be created and instead a user account with a configurable name to be employed and used instead for all other interactions with the vm (provisioning, login, etc). Typical Vagrant baseboxes come with preinstalled `vagrant` user (with default

Re: [vagrant-up] using a different username for provisioning

I'm asking for the `vagrant` user to not be created and instead a user account with a configurable name to be employed and used instead for all other interactions with the vm (provisioning, login, etc). Typical Vagrant baseboxes come with preinstalled `vagrant` user (with default