I had a look at this at some point but what I really dislike about Hammer as an API is that the JSON output is also capitalized and inconsistent. Ended up with large mappings and quickly gave up. Maybe I missed something and it can be done easily.

On Wed, Nov 29, 2017 at 09:35:46AM +0000, Sean O'Keeffe wrote:
Here's a radical thought, use Hammer...

Ansible modules do not have to be written in Python[2], although Ansible
does provide some nice shortcuts with Python, all that is really required
is JSON output... Some Ruby examples [1]
A couple of things to note if we were to entertain going down this route;
- How does DOCUMENTATION work for non-python modules? I played around for a
bit, but couldn't get ansible-doc to work..
- If the goal is to get them into Ansible core, will they accept Ruby
modules? Looking at Ansible core I think all the modules are python...


[1] https://github.com/ansible/ansible-for-rubyists
[2]
http://ansible-docs.readthedocs.io/zh/stable-2.0/rst/developing_modules.html

On Fri, Oct 27, 2017 at 8:11 PM, Michael Hofer <
michael.ho...@adfinis-sygroup.ch> wrote:

On Wed, 25 Oct 2017 08:09:10 -0400
Andrew Kofink <akof...@redhat.com> wrote:
[...]
> If given a choice, I would vote for Nailgun, a more mature project with
> more contributors and guaranteed future contribution from Satellite QA.
> There is a bit of a gap between foreman-ansible-modules and Nailgun,
given
> that it is not purpose built; for this, we do include
> ansible_nailgun_cement.py [1].
>
> I appreciate the support and interest from the community.

So far we've only used python-foreman in a few different projects, one to
configure Foreman based on a YAML file. We use python-foreman to resolve
the
IDs first thus the actual names of the templates, etc. can be used. Working
with the lib is nice but it still needs some glue because the API is
inconsistent and doing a lookup for the ID is not aligned for all
resources.

I have no experience with nailgun but from my point of view dependencies
are
not that big of a deal when provided as proper packages. E.g. to use the
Ansible mysql_db module you require python-mysqldb.

I'd love to switch to an upstream Ansible module to configure Foreman and
improve our existing playbooks.

Thanks for all the hard work so far!

--
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to