Rather than pick up code complexity for an alias feature, since this may confuse module developers - for this we're going to just rename them at some point with a future release.
I'm not positive it's time just yet. But soon. On Mon, Jun 16, 2014 at 2:49 AM, 'Petros Moisiadis' via Ansible Project < [email protected]> wrote: > On 06/15/2014 10:42 PM, Monty Taylor wrote: > > ... > > SO - and please tell me if I'm on crack here - would you be open to > > adding a general ansible feature similar to aliases but for module > > names? That way we could more gracefully handle renames that come up > > allowing people a transition period. > > ... > > I had not followed the thread at that time, but reading it now, I > wondered why nobody had not suggested that, until I saw your proposal. > Keeping backwards compatibility is good and is a must. Keeping backwards > compatibility and also not forcing to use or misleading users with > deprecated names or terms (or technologies) is even better. A > deprecation warning is a good addition for both old and new users. > > -- > 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/539EA19D.1070606%40yahoo.gr > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgyn%2BxM0jMwwbg7poSHpG3qb_i1%3DchXh-dtQP2TtxJMw9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
