On Sunday, September 14, 2014 2:39:27 AM UTC+7, Michael Peters wrote: > > But renaming the variables in either one would cause problems for > existing playbooks, so it would need to keep the old names around for > existing uses. This could lead to some confusion as the hostvars will > be polluted with duplicate entries and there's no real way to > encourage people to use the "right" names for the vars. >
There should be a deprecation period where names to be phased out are still supported, indeed. On the bright side, maybe, is that I imagine most people vendor a copy of ec2.py, it's awkward to try to symlink it or something from the Ansible distribution on different working environments and production control hosts. So in that case, upgrading the inventory plugin is a very conscious move. > IMO the ec2.py script should be changed to match the ec2_facts module > as the latter is an official part of ansible and the former is often > referred to as a "starting point" for your own inventory scripts. > That's probably the way to go, given the above assertion about ec2.py being a conscious upgrade decision for most, and also that it doesn't use the ansible_ namespace convention expected of official stuff. -Ches -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7a4eadfe-9916-4ba3-96b3-10e9236a13ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
