Welcome. That timeframe sounds about right unfortunately. You need to
chase up people on IRC, here, and on Github to manually
test/review/validate your changes. There's a huge stack on issues/PRs
and just submitting it and hoping someone will look at it is not enough
(although there is a process
My two cents. I think you're on the right track! There isn't much out
there for this specifically in Ansible that is obvious.
I do know that testinfra was created to test against specific states, so
you can make verification steps, if that is useful:
https://testinfra.readthedocs.io/en/latest/
for users
converting an inventory script to an inventory plugin:
[1]https://github.com/ansible/ansible/pull/44727
That might be of use (Note: I haven't yet read through the changes)
On Mon, Aug 27, 2018 at 4:34 PM Luke Murphy <[2]luk...@riseup.net> wrote:
Hi folks,
Following
OK, after some out-of-band mail, we're kicking this off!
Community issue:
https://github.com/ansible/community/issues/365
There's a PR that already needs a review if time permits:
https://github.com/ansible/ansible/pull/45902
Best,
Luke
On 0, Marques Johansson wrote:
Hi, Luke!
some work when we have time via IRC in the
beginning and if more come, we can do meetings etc. If that doesn't
work, all good. Can just ping by mail or what not.
On 0, Andrew Latham wrote:
I can spare some cycles on this if needs be.
On Thu, Sep 20, 2018 at 2:43 PM Luke Murphy <[1]
Hi folks,
I'm currently one of the maintainers of the Linode module and currently
working on a new one to support the new version 4 of the API. I have
some plans for new modules based on this new API all around automating
Linode with Ansible.
I just saw https://github.com/ansible/community and
Thanks to you both! That documentation PR is certainly helpful, I think
I have enough to push forward writing that inventory plugin now :)
On 0, Brian Coca wrote:
To clarify, unlike inventory scripts, inventory plugins don't 'return'
a format, they update the inventory itself.
--
