We split our ec2 environment into separate vpcs and until now, have been deploying to each via our own laptops. (Limited to credentials root users, 2)
I ran into an issue today where I did the following: ansible-playbook -i inventories/staging myawesomeplaybook.yml *Runs playbook on staging instances as expected ansible-playbook -i inventories/production myawesomeplaybook.yml !Runs playbook on staging instances when should actually be production Clearing out the ec2 cache resulted in the correct behavior, but this seems like a very dangerous characteristic. Is there an idiomatic way of handling differing staging from production inventories in EC2? -- 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 post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5e190604-abf6-4b13-8d94-6fc3ffff37de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
