Re: [foreman-dev] Community template repository labels

Hello, labels might help so +1 for that. I plan to send a PR with new directory structure as discussed at [1] soon. It might help the bot to just check the directories of touched files. [1] https://groups.google.com/forum/#!topic/foreman-dev/bzfBWEtIMpg -- Marek On pátek 13. ledna 2017

Re: Re: [foreman-dev] Revert removal of @host.params for host_param

+1 for keeping the macros. IMHO, just because we did something a certain way for a long time should not prevent us from changing it if there are reasons for a change. This is also not the first change in core that affected plugin(s) in a negative way and I doubt it will be the last. Breaking

Re: [foreman-dev] HoundCI - annoying?

I feel actually quite the opposite, we used to have Hound via some external service and this feels much better integrated. Since github introduced reviews, Hound integration could take advantage of it in the future? They will implode once a review is confirmed, that could help. On the other hand,

Re: [foreman-dev] Revert removal of @host.params for host_param

I am also for keeping the change but giving more attention to the upgrades and providing some tooling to convert existing templates. LZ On Wed, Jan 11, 2017 at 5:05 PM, Daniel Lobato Garcia wrote: > Hi foreman devs, > > Just noticed today

[foreman-dev] Puppetdb Plugin Options Update .

Hi All , PuppetDB plugin has new version which bring a lot of interesting parameters to get puppetdb.4.3 working properly . like ssl-ca and etc. Please can someone send me docs how to add (or create pull request) to this params. If you have time enough to do that it`s also perfect for me .

Re: [foreman-dev] .ISO deploys with Discovery

Thanks Greg, that's what I want to work on this week :-) More on this topic, we already have integration of Foreman Bootdisk with VMWare. You create new VM, that gets Bootdisk attached as an ISO file automatically and boots into Anaconda directly without PXE or DHCP. This might be interesting for

Re: Re: [foreman-dev] Revert removal of @host.params for host_param

Hi, I think that while there are benefits to moving away from the host object, we have a de-facto API based on it. A way to change without breaking user's template would be to use a "proxy" object that maintains the same endpoints and allows adding functionality or handling changes in the

[foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

Hi, I recently started identifying problematic areas in Permissions and Roles, especially with regard to plugins. Foreman provides 'Viewer' and 'Manager' roles out of the box and users expect these roles to work for plugins as well. But plugins generally do not add their permissions to core's

Re: [foreman-dev] Revert removal of @host.params for host_param

Hello The discussion has diverged into something different. People agree we should add an extra layer but implemented through proxy objects. It's also clear no one starts actively working on this right now. At the same time I want to add new macro, let's say rpm_distro? which returns

[foreman-dev] Foreman plugin accessing katello host data like asigned content view

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. regards, Daniel -- You received