The behavior is the same if I specify -i ec2.py. I like to specify
inventory manually instead of making it a global setting. Are you saying
the yml should call the python script?
On Thu, Dec 13, 2018 at 10:07 PM Tony Chia wrote:
>
>
> That is expected.
>
> If you don’t specify -i how the ansible
That is expected.
If you don’t specify -i how the ansible-playbook know you want to run against
production or staging or test env ?
You could probably set some defaults using the inventory setting under
defaults section in ansible.cfg. For example
https://raw.githubusercontent.com/ansible
Im unsure of what the problem is since you seem to have contradictory
expectations, you state info should be picked from
`"production/host_vars/hostname-stage.fqdn.yml` but that file is not
under production, but under staging.
In any case you can use `ansible-inventory` to see what ansible
actual
Hi all, first time posting, so apologies if I miss something.
I'm working on organizing an inventory folder for a multistage environment
and would like verification on whether the way I expect to work is true, or
if I'm missing something.
*Objective*
Using the following inventory folder struct
