Re: [foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-19 Thread Ewoud Kohl van Wijngaarden
On Thu, Jan 19, 2017 at 06:04:58PM +0100, Ivan Necas wrote: > Lukas Zapletal writes: > > >> > >> I'm not sure I follow what you mean by administrative tasks. Note that > >> reports > >> import and puppet envs import are core actiones that now run as a foreman > >> task > >>

[foreman-dev] Is this the new UI style from patternfly?

2017-01-19 Thread Tom McKay
I was making a role filter and see that the UI table is very different than other pages[1]. Is this what we should update the katello pages to as well? I couldn't find equivalent on patternfly.org. [1] http://www.awesomescreenshot.com/image/2080169/0a330d7663bc9617fbe28e2ac49b -- You

Re: [foreman-dev] Community template repository labels

2017-01-19 Thread Ewoud Kohl van Wijngaarden
https://github.com/theforeman/prprocessor/pull/55 should implement this, but it's pending the refactor Marek mentioned. On Mon, Jan 16, 2017 at 09:21:13AM +0100, Marek Hulán wrote: > Hello, > > labels might help so +1 for that. I plan to send a PR with new directory > structure as discussed at

Re: [foreman-dev] cosmetic yumrepo issue in foreman-infra causing large amount of cron mail

2017-01-19 Thread Greg Sutcliffe
On Thursday, 19 January 2017 16:45:00 GMT Ewoud Kohl van Wijngaarden wrote: > Pretty sure adding a name should be all. I'd recommend the same as the ID > now to prevent duplicate resources Thanks, https://github.com/theforeman/foreman-infra/pull/271 submitted. Greg -- You received this message

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

2017-01-19 Thread Ivan Necas
Lukas Zapletal writes: >> >> I'm not sure I follow what you mean by administrative tasks. Note that >> reports >> import and puppet envs import are core actiones that now run as a foreman >> task >> (both synchronous and asynchronous variants). By making the UI part >> optional

Re: [foreman-dev] cosmetic yumrepo issue in foreman-infra causing large amount of cron mail

2017-01-19 Thread Ewoud Kohl van Wijngaarden
Pretty sure adding a name should be all. I'd recommend the same as the ID now to prevent duplicate resources > On 19 Jan 2017, at 16:29, Greg Sutcliffe wrote: > > I'm getting a lot of mails from the slaves at the moment like the one below. > I'm not super-familiar

[foreman-dev] cosmetic yumrepo issue in foreman-infra causing large amount of cron mail

2017-01-19 Thread Greg Sutcliffe
I'm getting a lot of mails from the slaves at the moment like the one below. I'm not super-familiar with the 'yumrepo' puppet resource, but does it just need a 'name' parameter added to this block? https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/slave/

Re: [foreman-dev] Puppetdb Plugin Options Update .

2017-01-19 Thread Ewoud Kohl van Wijngaarden
On Mon, Jan 16, 2017 at 03:01:23AM -0800, Karen Harutyunyan wrote: > 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

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

2017-01-19 Thread Marek Hulán
On úterý 17. ledna 2017 14:45:53 CET Ondrej Prazak wrote: > On Tue, Jan 17, 2017 at 12:08 PM, Tomas Strachota > > wrote: > > On Mon, Jan 16, 2017 at 6:55 PM, oprazak wrote: > > > Hi, > > > I recently started identifying problematic areas in Permissions