bcoca

5 ms·

1.
by bcoca 10y ago
yes, many times we need to work 'around' the tools as they do not do what we want and cannot disable to avoid confusion: https://github.com/ansible/ansible/releases
2.
by bcoca 10y ago
As an OSS maintainer that is currently struggling with this I can tell you the solutions are not that simple: - We use several mailing lists (like a forum its good for async communication) - We have several IRC channels for immediate feedba
3.
by bcoca 10y ago
because it uses existing interpreters on the target host, fixed locations only happen in a homogeneous environment. Most IT shops commonly have to deal different OS/Distrbutions/Versions so the same way you cannot have just 1 tshi
4.
by bcoca 10y ago
actually, the 'controller' specifies the interpreter to be used at the client, there can be more than 1 and the '1st one in path' is not always the correct one.
5.
by bcoca 10y ago
it is not a host definable fact, it is a 'host variable' which you normally define in inventory.
6.
by bcoca 10y ago
disclaimer: I'm one of the maintainers I'll try to answer several questions so this might get long. First, the procedure for disclosing the CVE is something we discussed internally (including security professionals), as all over t
7.
by bcoca 10y ago
minors we release every 3-4 months (or plan to)
8.
by bcoca 10y ago
speed has been both better and worse, so depends a lot on what your playbook is doing, size of your inventory, vars, etc the only answer i can give you is: test. We do try to keep decent performance, but this is not our main focus.
9.
by bcoca 10y ago
we actually avoid the requests lib for this and many other reasons, we don't use libcurl as we try to avoid extra dependencies when possible. The issue is more basic than requests, the actual python http/url and ssl implementation
10.
by bcoca 10y ago
Support for python3 has been on the roadmap, sadly most of the installed base of servers out there uses 2.x and in many cases 2.4 (centos/rhel5). This is NOT a switch from py2 to py3 we are aiming to support BOTH at the same time, this
11.
by bcoca 10y ago
disclaimer: i'm an ansible dev. As the ticket shows, this was added in the 2.x release of Ansible, that is why the ticket was closed. Adding this info required a major revamp of the parser, which we did in 2.x, for this and many other