It seems I reject this mail by mistake, forwarding to the list to
restart the conversation.
···
---------- Forwarded message ---------- From: juraj.funcik@gmail.com To: foreman-dev Cc: Bcc: Date: Fri, 14 Jul 2017 05:44:44 -0700 (PDT) Subject: Proposal/Request - Foreman Ansible plugin - Dynamic inventory parameters definition Hi,first of all, I’d like to thank you for the great work you’ve done so
far. I really admire all of you guys.
My programming skills are not so good so I’ll only lend my hand in
proposing an idea or two that might be useful.
Before I run Ansible role directly I can specify certain connection
parameters in an Ansible inventory file.
As you know the same option is available in the Foreman GUI interface
via parameters (Global parameters, Host group parameters etc.).
However, there is one limitation and that is the list of parameters
administrators can specify is limited. To get an idea which parameters
are available
one can take a look in the following ruby scripts
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-1.4.5/app/services/foreman_ansible/inventory_creator.rb
and
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-1.4.5/app/models/setting/ansible.rb
.
The problem arise when somebody needs a parameter that is not listed
there. Okay, you can edit both above mentioned scripts and then
restart Foreman,
but every time the official update is applied, you have to add all
necessary code changes again. This sucks and I believe everyone agrees
with me.
So the idea I’d suggest is that, let administrators define what
parameter they need/want without hard-coding into Foreman Ansible
plugin ruby scripts, OR
make them hard-coded but the list of available parameter must be complete.
What do you think?