[ansible-project] ansible-galaxy github-token calling non-existant API endpoint

Hi there, it seems an API endpoint may have vanished. >From - http://docs.ansible.com/ansible/galaxy.html Authenticate with Galaxy "If you do not wish to use your GitHub password, or if you have two-factor authentication enabled with GitHub,

[ansible-project] stopping ec2 spot instances

I'm writing an ansible demo, showing how to provision Riak clusters, and I want to make it super self contained. With that in mind, I’ve been playing with the ec2.py inventory script, and the ansible ec2 module. Starting the nodes works great (if anyone is interested, I'm happy to share the

Re: [ansible-project] Last round of testing for -c ssh_alt before promoting to the new -c ssh

I'd like to take this back, ssh agent forwarding does work. I have discovered that it only fails in relation to the git module. On Tuesday, February 25, 2014 10:16:53 AM UTC, bryan hunt wrote: My problem was specifically with SSH Agent authentication failing to propagate to SSH invoked

Re: [ansible-project] Re: file in vault (ssh private key)

I'd like to take this back, ssh agent forwarding does work. I have discovered that it only fails when used by the git module. Running commands which use ssh from Ansible does work. On Wednesday, March 5, 2014 5:11:50 PM UTC, Jeremy Schneider wrote: On Wed, Mar 5, 2014 at 10:59 AM, bryan hunt

Re: [ansible-project] Re: New URI module from Romeo Theriault

Thanks Romeo, I have recreated a pull request. https://github.com/ansible/ansible/pull/6649 On Friday, March 21, 2014 5:45:45 PM UTC, Romeo Theriault wrote: On Fri, Mar 21, 2014 at 6:38 AM, bryan hunt picsol...@gmail.comjavascript: wrote: Yes, but there are two valid results, either 409

[ansible-project] Re: New URI module from Romeo Theriault

I have this same issue when using it to create riak-cs admin users. riak-cs will return either 201 or 409 when sending a PUT request, never a 200. Unfortunately 201 triggers module failure, as 200 is what it expects. riak_cs | FAILED **msg: Status code was not 200, I can work around

[ansible-project] Re: New URI module from Romeo Theriault

I have this same issue when using it to create riak-cs admin users. riak-cs will return either 201 or 409 when sending a PUT request, never a 200. Unfortunately 201 triggers module failure, as 200 is what it expects. riak_cs | FAILED **msg: Status code was not 200, On Monday, October 7,

Re: [ansible-project] Re: New URI module from Romeo Theriault

Yes, but there are two valid results, either 409 or 201. On 21 Mar 2014, at 15:03, Michael DeHaan mich...@ansible.com wrote: There's a status_code option you can send. http://docs.ansible.com/uri_module.html On Fri, Mar 21, 2014 at 10:55 AM, bryan hunt picsolvebr...@gmail.com wrote

[ansible-project] Re: Serving files from a central asset server

I'm always in favor of using the right tool for the job, is this not the sort of task at which rsync excels? An rsync module perhaps? -- You received this message because you are subscribed to the Google Groups Ansible Project group. To unsubscribe from this group and stop receiving emails

[ansible-project] Ansible Galaxy roles - distro - arch 64

I created a (trivial) role to install Docker onto Ubuntu Precise, and amended the meta/main.yml file appropriately. There is an issue though, this role only works on Ubuntu Precise 64bit. AFAIK, Docker do not supply 32 bit debs for their service. I can't figure out how to express this, is

Re: [ansible-project] Ansible Galaxy roles - distro - arch 64

Yeah Paul, I like. I'll add it now. Good suggestion. Thanks, Bryan On 26 Feb 2014, at 16:59, Paul Durivage paulduriv...@gmail.com wrote: If you so choose, you could add a task to the role to ensure the system is a 64-bit system. - name: Ensure system is x86_64 fail: msg=Docker requires

Re: [ansible-project] Last round of testing for -c ssh_alt before promoting to the new -c ssh

/21972438/getting-rsync-in-ansible-to-work-with-vagrant On Wednesday, 8 January 2014 09:15:04 UTC-8, bryan hunt wrote: That was a stack overflow post I created, I've been trying to figure out for the last 3 weeks why I couldn't check out a project (R/W) from github using Ansible. Finally, I

[ansible-project] Re: Ansible or Salt?

For - neither is implemented in Ruby. Against - neither has (yet) achieved world dominance. On Tuesday, February 4, 2014 8:18:58 PM UTC, Bill King wrote: I'm just starting to explore both Ansible and Salt. I'm hoping folks can offer some insights as to a pros-cons of Ansible vs. Salt.

[ansible-project] Re: EC2 provisioning with Ansible

You might need to use the Vagrant to boot the EC2 instance with Ansible performing the provisioning step. Bryan On Monday, January 13, 2014 3:32:26 PM UTC, howa...@gmail.com wrote: Is it possible to fully automatic launch an EC2 instance and run the playbooks against this instance, with

[ansible-project] Re: Ansible Tasks reusability

I had no idea that was possible, I've been using all sorts of kludges to achieve the same. On Monday, January 13, 2014 6:17:55 PM UTC, Adam Morris wrote: On Tuesday, January 7, 2014 1:38:06 AM UTC-8, hafizh wrote: I notice that the tasks are very 'strict'. Once we provide an optional

Re: [ansible-project] Reporting changed state by email

It would be nice if ansible-galaxy had support for distributing these sort of plugins. On Friday, January 10, 2014 9:38:38 AM UTC, JP Mens wrote: Thanks for these pointers JP. The mail plugin looks interesting, and is probably what I need. How do I call it from a playbook though? You

Re: [ansible-project] Last round of testing for -c ssh_alt before promoting to the new -c ssh

. (It's also not ssh_alt specific so it shouldn't block forward progress on this front) On Wed, Jan 8, 2014 at 11:06 AM, bryan hunt picsolvebr...@gmail.com wrote: I've been doing a lot of research on why I couldn't get ssh forwarding to work with Ansible. I think I've found

Re: [ansible-project] possible bug with users

positive we would have heard about it 1000x over, but this list is for helping people out with questions. I would only ask that people not first assume they have found a bug, but instead ask for help with a problem. On Thu, Jan 2, 2014 at 6:05 AM, bryan hunt picsol

Re: [ansible-project] possible bug with users

Yes. Well surmised. Is there any way to re-trigger the gathering inside a playbook? On 3 Jan 2014, at 14:55, Brian Coca brianc...@gmail.com wrote: ansible_env gets set when facts are gathered and of course user variables depend on which user was used to gather those facts. -- Brian

Re: [ansible-project] possible bug with users

:00:22 PM UTC, bryan hunt wrote: Yes. Well surmised. Is there any way to re-trigger the gathering inside a playbook? On 3 Jan 2014, at 14:55, Brian Coca brianc...@gmail.com wrote: ansible_env gets set when facts are gathered and of course user variables depend on which user was used

[ansible-project] possible bug with users

Hi there, I'm running via Vagrant, so everything should be executing by default as vagrant user. My configuration looks like this config.vm.provision ansible do |ansible| ansible.playbook = ../playbooks/docker.yml ansible.sudo = true ansible.host_key_checking = false

Re: [ansible-project] Proposal to add ansible_ssh_config inventory parameter

Sorry to resurrect an old post. I'm trying to get ansible/vagrant integration working. Vagrant uses a generated inventory file to communicate with Ansible. But it is not setting Ansible to perform agent forwarding. On Wednesday, August 7, 2013 2:53:20 AM UTC+1, Michael DeHaan wrote: