Hi James,
Sure. Here's the issue:
https://github.com/ansible/ansible-modules-core/issues/452
I'd also like to suggest a few parameters for the rds module:
- storage type (something like standard, gp2, io1)
- publicly accessible (yes/no)
I already have a few PRs scheduled for this weekend so not
Just upgraded to 1.8.2 and noticed a change in behavior (previosuly on
1.7.2)
delegate_to only works when the host we wnat to delegate to is in the
current inventory, is this intentional? It was working fine on 1.7.2
Also, another delegate_to apparent change... we previously used
Can add that we have downgraded to 1.8.1 and both things appear to work
fine..
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Thanks Tim, there was a bugfix related to delegate_to in this release,
which may have created this bug. We'll look into this today.
On Fri, Dec 5, 2014 at 7:27 AM, Tim Rice timric...@gmail.com wrote:
Can add that we have downgraded to 1.8.1 and both things appear to work
fine..
--
You
delegate_to only works when the host we wnat to delegate to is in the
current inventory, is this intentional? It was working fine on 1.7.2
Ok, doesn't sound to be super breaking, but we're on it. Thanks for the
report.
On Fri, Dec 5, 2014 at 6:43 AM, James Cammarata jcammar...@ansible.com
I use jenkins heavily for orchestration, in a setup where I have multiple
jenkins CD pipelines in different environments all deploying code using
Ansible.
See this setup below, it's an example for deploying jenkins, setting up the
jobs and dependencies.
It also shows how to provisioning and
Hi all. Are you an Ansible fan and want to talk about the great stuff
you're doing with Ansible -- and also planning to be at FOSDEM and/or
cfgmgmtcamp.eu in Belgium in late January / early February?
If you're interested, please submit a talk at one/both. NOTE:
submission deadlines for each have
Hello,
when you have a lot of roles, it might be feasible give them a
structure. What's the preferred way in ansible?
Using directory hierarchies like roles/fizz/buzz or dots roles/fizz.buzz?
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
Dot notation is currently used by Galaxy, however the namespaces there are
typically usernames.
Ansible doesn't necessarily support nested role directories like you
mention, so I am going to stick with dot notation.
It's really just a directory name with a period in it at that point.
To
Sure, I've been using {{ hosts }} - I just copied the example from the old
docs - sry for that. I did some more testing and think this is a bug. I
reported it with a simple example playbook at
https://github.com/ansible/ansible/issues/9733
Am Freitag, 5. Dezember 2014 01:56:26 UTC+1 schrieb
or check out Tower :)
On Fri, Dec 5, 2014 at 9:50 AM, Azul Inho m...@azulinho.com wrote:
I use jenkins heavily for orchestration, in a setup where I have multiple
jenkins CD pipelines in different environments all deploying code using
Ansible.
See this setup below, it's an example for
Ansible doesn't necessarily support nested role directories like you
mention, so I am going to stick with dot notation.
Ansible can check out role paths anywhere you want, you'll just have to
configure the roles path in ansible.cfg OR stick the / in there when
referring to the role name.
On
Where did you define the 'my group' variable?
On Fri, Dec 5, 2014 at 2:48 PM, Wolfgang Ziegler nup...@gmail.com wrote:
Sure, I've been using {{ hosts }} - I just copied the example from the old
docs - sry for that. I did some more testing and think this is a bug. I
reported it with a simple
13 matches
Mail list logo
