Ok, I managed to fixed with what you and Shawn said, but why the following
happens:
When I define this in my playbook:
vars:
include: /etc/ansible/add_users/global_vars/main.yml
And then I have the following in my vars file:
---
#wheelsregex: # *%wheel *ALL=\(ALL\) *ALL
#user_password:
Please ignore the differences in user names and public keys, they're the
same (I used to change the names in this thread only).
--
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,
Replying to myself.
Well, it was just integer vs. string in the end. So yeah, PEBKAC. Quoting
everything in proxy_to_app_map did the trick.
Regards,
Daniel
On Friday, July 17, 2015 at 6:29:36 PM UTC+1, Daniel Siechniewicz wrote:
Hi,
I'm using ansible[-playbook] 1.9.0.1.
I have 4 proxy
FWIW, this might come in handy if you're using
ElastiCache: https://github.com/ansible/ansible/pull/11261
My pal decided that this might ease our work and boy he was right :)
On Tuesday, 5 May 2015 01:34:39 UTC+2, DenMat Gone wrote:
On Tuesday, May 5, 2015 at 6:32:21 AM UTC+10, Brian Coca
see
here: https://groups.google.com/d/msg/ansible-project/qJ2UNWuaIJk/-S0GyDfTbPoJ
On Tuesday, 5 May 2015 02:12:31 UTC+2, DenMat Gone wrote:
Thanks Matt,
You're correct.
On Tuesday, May 5, 2015 at 12:19:16 AM UTC+10, Matt Martz wrote:
Case matters when accessing keys.
Instead of
vars:
include: /etc/ansible/add_users/global_vars/main.yml
^ that does not work, you want:
vars_files:
- /etc/ansible/add_users/global_vars/main.yml
https://docs.ansible.com/playbooks_variables.html#variable-file-separation
include is for plays or tasks, for vars you have vars_files or
I'm trying to use galaxy roles for the first time and started with
installing the geerlingguy.logstash role on an Amazon Linux Instance.
It mostly seems to work, at least up until it gets to the repo-epel role
Im getting:
TASK: [geerlingguy.repo-epel | Install EPEL repo.]
There's no set reason. There is an open pull request to add support
for additional hashes:
https://github.com/ansible/ansible-modules-core/pull/141
I've reviewed it -- it needs some revisions and then could be merged.
I don't have time before v2 to make the revisions myself but perhaps
someone
Galaxy roles are maintained by individual contributors in the Ansible
community.
On the web page for each role, there's a link to the Github repo,
where you can contact the author directly. That would be my advice.
--g
On Mon, Jul 20, 2015 at 2:04 PM, Bob Brown b...@timevest.com wrote:
I'm
On Jul 16, 2015 12:53 PM, Timothy Appnel t...@ansible.com wrote:
I wouldn't recommend just dropping your library in to just /tmp to avoid
a potential conflict with another job or process. Perhaps create a separate
directory like the name of your project or playbook under tmp and store it
there?
Hello,
I would like to know if it is possible to get OS information from the AWS
ec2 dynamic inventory script? Like OS distribution. Or how do you get OS
information before sshing the host?
Thank you.
B.R.
--
You received this message because you are subscribed to the Google Groups
Hello Brian,
I have made some tests and it seems that hosts conditional it is not
working for the instances that cannot login (either root or fedora, tested
both).
First test:
If i create the group according to fedora access rules, the group for the
centos instances it is not created:
---
You could modify the ec2.py script so that it checks he ec2_image_id and
does some logic based around the OS associated with the ec2_image_id.
On Monday, July 20, 2015 at 5:16:54 PM UTC-4, Adam R. wrote:
Hello,
I would like to know if it is possible to get OS information from the AWS
ec2
Hi just quick question - I noticed the latest documentation the feature to
use a string content for the file content in copy module is no longer
listed. Is it dropped in latest ansible?
I use it heavily for copying ssh key etc.. (encode b64 and decode back) if
it is dropped then it would be
Brian,
Thanks for the clarification.
Andrew
On 15 July 2015 at 13:34, Brian Coca bc...@ansible.com wrote:
not really, since you could have 10 diff plays for adding cron,
ansible won't know about the other 9 when running 1, it is up to you
too keep track. I just normally create 1 off plays
15 matches
Mail list logo