I'm generally interested if it is possible to access from within a
foreman_plugin data from Katello plugin (plugin accesses data from other
plugin).
For example I would like to extract the content-view/asigned repository
information for a given host.
> Hi All,
>
> I'm generally interested if it is possible to access from within a
> foreman_plugin data from Katello plugin (plugin accesses data from other
> plugin).
> For example I would like to extract the content-view/asigned repository
> information for a given host.
Yes, after initialization your plugin should be able to access all
katello properties.
The foreman-docker plugin for instance does different things depending
on whether Katello is available or not, like in:
If there is any specific data that you aren't sure about, feel free to ping
and ask here. Ruby allows you access to almost anything, and there are
certainly some better practices we've discovered over the years for how and
where to do this access to reduce the chance of breakage between releases.
We would also find it interesting to see where and what you';d like
"supported" access to in case that presents an opportunity to build a
supported API for plugin access to Katello.
Eric
···
On Tue, Jan 17, 2017 at 6:39 AM, Daniel Lobato Garcia wrote:
On 01/16, Daniel Kuffner wrote:
Hi All,
I’m generally interested if it is possible to access from within a
foreman_plugin data from Katello plugin (plugin accesses data from other
plugin).
For example I would like to extract the content-view/asigned repository
information for a given host.
Yes, after initialization your plugin should be able to access all
katello properties.
The foreman-docker plugin for instance does different things depending
on whether Katello is available or not, like in: