Tomas,
Here's the issue: http://projects.theforeman.org/issues/15830
The affected commands are quite widespread. Since the 6.2 release, there
have been 2 bug reports that duplicate 15830. Any command that has content
views or lifecycle environments as a non-primary option with ID resolution
(i.e.
Hi Andrew,
searchables are meant to be used only for storing alternative
identifiers for a resource. That's why they're always prefixed in
options. Together with *_id params from index action of the resource
they create compound identifier. I understand it makes it very difficult
to use in yo
Foreman Community:
Today Red Hat released Satellite 6.2. The official press release will go
out tomorrow, but you can read about the release at [1]. This version of
Satellite is based off of Foreman 1.11 and several of the plugins. The
success of Red Hat Satellite is based on the hard work and
On 07/26/2016 02:52 PM, Partha Aji wrote:
Not sure who is working on the Ansible Integration story, do we know if
we plan to serve and manage ansible playbook recipes via pulp similar to
the way we do Puppet Modules?
Partha
Long term yes, short term, no.
- bk
--
You received this message
We’d need pulp to add Ansible support and I think (don’t quote me) that
they are waiting until Pulp 3.0+ since 3.0 will be a major rewrite to Pulp.
Maybe someone from Pulp can chime in though.
David
On Tue, Jul 26, 2016 at 2:52 PM, Partha Aji wrote:
>
> Not sure who is working on the Ansible I
On 19 July 2016 at 11:20, wrote:
> Hi all
>
> Demo time is upon us once again...
>
Reminder, this is *tomorrow*. So far we have ~20min of content (thanks lzap
and inecas), so I've still got plenty of space.
Thanks!
Greg
--
You received this message because you are subscribed to the Google Gro
On 07/21, Daniel Lobato Garcia wrote:
> Hi devs,
>
> Just wanted to give you an update on packaging for npm & webpack
> incidentally. We have two PRs in core that are dabbling in a more modern
> way of doing frontend development in Foreman.
> https://github.com/theforeman/foreman/pull/3433
> https:
I guess this should be enough to allow us staring using the backlogs
plugin again
https://github.com/theforeman/prprocessor/pull/48
-- Ivan
On Wed, Jul 27, 2016 at 11:17 AM, Ivan Necas wrote:
> On Wed, Jul 27, 2016 at 11:08 AM, Marek Hulán wrote:
>> On Wednesday 27 of July 2016 09:09:20 Domini
Hello,
TL;DR - your plugin might be incompatible with develop branch soon, this
explains how to fix it.
Dominic's patch which moves from the protected_attributes gem to
strong parameters in controller concerns is RTM. Some plugins will need
to be updated in order to remain compatibility with deve
On Wed, Jul 27, 2016 at 11:08 AM, Marek Hulán wrote:
> On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote:
>> On 27/07/16 08:54, Marek Hulán wrote:
>> > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:
>> >> I've deleted the the "Team AL-GTD - 1" version that somebody had added
>> >>
On Wed, Jul 27, 2016 at 11:27 AM, Tomas Strachota
wrote:
> +1 for option 4. From what I saw it's common approach in other projects.
> It's simple enough for start and we can re-evaluate later if we find it
> problematic.
>
due to the fact that number 3 is not that simple either, I'm starting to
On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote:
> On 27/07/16 08:54, Marek Hulán wrote:
> > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:
> >> I've deleted the the "Team AL-GTD - 1" version that somebody had added
> >> to the Foreman project in Redmine, as it's project-wide and
+1 for option 4. From what I saw it's common approach in other projects.
It's simple enough for start and we can re-evaluate later if we find it
problematic.
T.
On 07/26/2016 05:25 PM, Tomer Brisker wrote:
Hi,
I meant to reply to this much sooner but it somehow slipped between the
cracks.
Fi
On 07/26/2016 05:25 PM, Tomer Brisker wrote:
Hi,
I meant to reply to this much sooner but it somehow slipped between the
cracks.
First, a big thank-you to Daniel for all the effort put into getting
this done.
I think either 3 or 4 make the most sense, but at this point anything
that will let us
On 27/07/16 08:54, Marek Hulán wrote:
> On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:
>> I've deleted the the "Team AL-GTD - 1" version that somebody had added
>> to the Foreman project in Redmine, as it's project-wide and so is set on
>> every issue.
>
> Hello
>
> Could you please elab
On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:
> I've deleted the the "Team AL-GTD - 1" version that somebody had added
> to the Foreman project in Redmine, as it's project-wide and so is set on
> every issue.
Hello
Could you please elaborate a bit why this is considered bad? I planned t
16 matches
Mail list logo