[ansible-project] Re: Issues with specifying group vars with a dynamic EC2 inventory

2020-02-03 Thread Justin Madill
Well I've found a solution that also fixes the volatility issue by adding a 
group_vars folder beside my playbooks in the project then I can use the 
standard vault variable syntax as well.

On Monday, 3 February 2020 15:05:31 UTC-7, Justin Madill wrote:
>
> I am currently running Ansible 2.9.1 and Tower 3.6.2
>
> On Monday, 3 February 2020 14:55:33 UTC-7, Jordan Borean wrote:
>>
>> This sounds like it was potentially fixed with 
>> https://github.com/ansible/ansible/pull/65023 which has been backported 
>> to Ansible 2.9. What Ansible version are you running?
>>
>> Thanks
>>
>> Jordan
>>
>

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/a76834d8-d17e-4cb5-be7e-799876514cef%40googlegroups.com.


[ansible-project] Re: Issues with specifying group vars with a dynamic EC2 inventory

2020-02-03 Thread Justin Madill
I am currently running Ansible 2.9.1 and Tower 3.6.2

On Monday, 3 February 2020 14:55:33 UTC-7, Jordan Borean wrote:
>
> This sounds like it was potentially fixed with 
> https://github.com/ansible/ansible/pull/65023 which has been backported 
> to Ansible 2.9. What Ansible version are you running?
>
> Thanks
>
> Jordan
>

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/49bd49c3-5bee-468a-9a7f-489634ac9bcc%40googlegroups.com.


[ansible-project] Issues with specifying group vars with a dynamic EC2 inventory

2020-02-03 Thread Justin Madill
I'm currently building out a PoC with Ansible Tower to manage our primarily 
windows environment.
I've had everything working from the command line before starting with 
Tower, that that was using a static inventory.

The problem I'm having right now is finding a method for specifying the 
connection variables for windows servers (without also having them applied 
to non windows servers).
The variables I need to setup are:

ansible_user: ansi...@mydomain.ad
ansible_password: >-
!vault | $ANSIBLE_VAULT;1.1;AES256

35663130633434366336353562303031613263663936653164383937353362643531343561373365

616566356561353137333166613062663631356630340a393764666466346165316337626336

39353764316532693166323931363264363137343466343563613663366434313261623265643066

3130313935343866350a346166363061616338623662343763613630343362653061376465303835
6535
ansible_port: 5985
ansible_connection: winrm
ansible_winrm_server_cert_validation: ignore
ansible_winrm_transport: kerberos

I was able to manually add them to the ec2 tag based group that i've setup 
for the windows machines, and while they were picked up, it appears to not 
know that it needs to decrypt the password, and putting that vault value in 
with the standard syntax (no >- at the start) just throws a parsing error 
on save.
Though even if I do get this method working if we ever need to rebuild the 
inventory from scratch those values would be lost.

I have read through dozens of issue reports, blog posts, and google group 
posts on this topic and couldn't find any solutions or even other ideas to 
try.

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/d23af8e8-7d0b-4ca0-8f4d-d6097ed3387d%40googlegroups.com.