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

On úterý 24. ledna 2017 0:02:15 CET Ivan Necas wrote: > Lukas Zapletal writes: > >> If you're concerned about the permissions table, this does not help. > >> Permission are created there by plugin. If the permission is removed > >> later, it should be removed from all roles

[foreman-dev] Your input needed! Foreman Community Survey (2017 edition) is ready!

Hi all I'm happy to announce the 2017 community survey is now ready for your input! Tell us how you use Foreman, what's good/bad, and help us shape what the next year of Foreman looks like! https://goo.gl/forms/xswoDALeJFoPMcy73 This year we've gone to a multi-page format - mainly for

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

On Tue, Jan 24, 2017 at 12:10:34AM +0100, Ivan Necas wrote: > Ohad Levy writes: > > > On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal wrote: > > > >> Why we haven't considered ActiveJob API in the first place? This looks > >> like ideal solution, easy

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

Ohad Levy writes: > On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal wrote: > >> Why we haven't considered ActiveJob API in the first place? This looks >> like ideal solution, easy development and documented API. >> >> Can't ActiveJob help us with memory

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

Lukas Zapletal writes: >> If you're concerned about the permissions table, this does not help. >> Permission are created there by plugin. If the permission is removed later, >> it >> should be removed from all roles anyway, user could already assign it to both >> core and

Re: [foreman-dev] Broadening katello-deploy's horizons

Thanks for setting that up Daniel! On Jan 23, 2017 2:13 PM, "Daniel Lobato" wrote: > Team is ready at https://github.com/orgs/theforeman/teams/forklift > > On Sun, Jan 22, 2017 at 11:02 PM, Ivan Necas wrote: > > Eric D Helms

Re: [foreman-dev] Notifications API & UI available - quick HOWTO

On 01/23/2017 12:42 PM, Tom McKay wrote: Wish list... + Every notification we add to this system should be required to have a unique ID based on where it is in the code. This ID could be leveraged for access insights, docs, etc. (Maybe this is already the case?) +1 -- bk -- You received

Re: Re: [foreman-dev] Notifications API & UI available - quick HOWTO

Wish list... + Every notification we add to this system should be required to have a unique ID based on where it is in the code. This ID could be leveraged for access insights, docs, etc. (Maybe this is already the case?) + Dedicated notifications API/CLI/UI to manage notifications and messages

Re: [foreman-dev] Re: Draft community survey questions

On Friday, 20 January 2017 15:51:28 GMT Stephen Benjamin wrote: > Also "Smart proxy, Hammer & API" page - I think maybe adding "Katello" > in parens next to smart_proxy_pulp might help people know what it's > for. I doubt most Katello users are aware of the plugin name on the > smart proxy side.

Re: [foreman-dev] Plan for dropping Puppet 3 in the installer modules

On 01/23, Ewoud Kohl van Wijngaarden wrote: > Hello all, > > We should come up with a plan for dropping Puppet 3 in our installer > modules. > > Officially Puppet 3 is already EOL since 1-1-2017. We also know that > both puppetlabs and voxpupuli (our only dependencies) are dropping > Puppet 3

Re: Re: [foreman-dev] Notifications API & UI available - quick HOWTO

On 01/23, Tom McKay wrote: > Is there a dedicated page where these notifications are displayed? For > example, if I mark one as "read" and it disappears, where do I go to see it > in a history view? It doesn't dissapear, it's displayed but the group isn't in bold anymore and it will not display

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

> If you're concerned about the permissions table, this does not help. > Permission are created there by plugin. If the permission is removed later, it > should be removed from all roles anyway, user could already assign it to both > core and plugin role. Down below. > I suppose you wrote a

Re: [foreman-dev] Notifications API & UI available - quick HOWTO

Is there a dedicated page where these notifications are displayed? For example, if I mark one as "read" and it disappears, where do I go to see it in a history view? On Fri, Jan 20, 2017 at 12:08 PM, Lukas Zapletal wrote: > When ERROR message appears in Smart Proxy log buffer,

Re: [foreman-dev] Plan for dropping Puppet 3 in the installer modules

On 23/01/17 13:30, Ewoud Kohl van Wijngaarden wrote: > Officially Puppet 3 is already EOL since 1-1-2017. We also know that > both puppetlabs and voxpupuli (our only dependencies) are dropping > Puppet 3 support. > > That said we also know that many of our users are still on Puppet 3 and >

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

Thanks for update, sending few more comments below in text On pondělí 23. ledna 2017 12:48:46 CET Lukas Zapletal wrote: > > Sorry I don't get it, especially the price. What's the difference between > > core and plugins in terms of permissions upgrades? If you rename plugin > > permission you need

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

> Sorry I don't get it, especially the price. What's the difference between core > and plugins in terms of permissions upgrades? If you rename plugin permission > you need to provide the same migration as if you renamed it in core. Once we merge everything into core roles, there is no easy way