The API is not the product, the Ansible command line tools are, the API is there for the tool usage and it not the main interface. This has always been the case and stated in many occasions and in the documentation.
Runner was not simple (no class with a thousand+ line __init__ method is) and was full of errors as many features were 'bolted in' and was sorely needing a redesign. It might have been 'simple to call' but it was not easy to maintain nor extend. We removed runner and derived over a dozen classes that now handle the same functions in a much cleaner way internally. This also allowed us to correctly test the code and now validate plays, many previously silent errors are now caught. Adding new features is much simpler and clearly defined, as is the inheritance of such features, things are much more well defined and predictable. We also made many parts of the code more configurable and were able to push features to the plugins that were previously hardcoded. As much as this has made it easier to maintain and extend Ansible, it has made the API interface more complex, but that, again, is something that we use internally for the command line tools, which have not really changed their interface and maintained their simplicity. Long story short, NO we do NOT want runner back. It is easy enough to create other helper classes to simplify the interface for 3rd party, but it is not something the current project focuses on, our focus is the set of CLI tools which our main user base depends on. ---------- Brian Coca -- 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/CACVha7e3%2BLLcJpSq8%3DpzGMqKNfFtetVjcpiN6FcHQ9VTavUzdg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
