I think for MDP3, we're thinking of adding in auditing. My question is about the audited gem. I've used audited in the past (when it was known as acts_as_audited) and it was a solid gem. My concern though is that it's not very well maintained (like they still haven't added Rails 4 support[1]). I've also used the paper_trail gem[2] which I've had a lot of good experiences with and it looks like it's a little bit better maintained. I'm wondering if switching gems might be an option–assuming we could migrate data over, etc. I bring this up now because I think it's worth addressing before we integrate with Katello. Any thoughts would be appreciated.
> From: "David Davis" <daviddavis@redhat.com>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Sent: Wednesday, December 11, 2013 1:54:05 PM
> Subject: [foreman-dev] Auditing in Foreman
>
> I think for MDP3, we're thinking of adding in auditing. My question is about
Just a quick reminder that the community doesn't/shouldn't generally know about MDP3.
···
----- Original Message -----
the audited gem. I’ve used audited in the past (when it was known as
acts_as_audited) and it was a solid gem. My concern though is that it’s not
very well maintained (like they still haven’t added Rails 4 support[1]).
I’ve also used the paper_trail gem[2] which I’ve had a lot of good
experiences with and it looks like it’s a little bit better maintained. I’m
wondering if switching gems might be an option–assuming we could migrate
data over, etc. I bring this up now because I think it’s worth addressing
before we integrate with Katello. Any thoughts would be appreciated.
> From: "David Davis" <daviddavis@redhat.com>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Sent: Wednesday, December 11, 2013 1:54:05 PM
> Subject: [foreman-dev] Auditing in Foreman
>
> I think for MDP3, we're thinking of adding in auditing. My question is about
> the audited gem. I've used audited in the past (when it was known as
> acts_as_audited) and it was a solid gem. My concern though is that it's not
> very well maintained (like they still haven't added Rails 4 support[1]).
> I've also used the paper_trail gem[2] which I've had a lot of good
> experiences with and it looks like it's a little bit better maintained. I'm
> wondering if switching gems might be an option–assuming we could migrate
> data over, etc. I bring this up now because I think it's worth addressing
> before we integrate with Katello. Any thoughts would be appreciated.
(hit send too soon)
I think this work would generally be for 1.4 or 1.5. Possibly 2.0 whenever we decide to bump the major version.
>
>
> > From: "David Davis" <daviddavis@redhat.com>
> > To: "foreman-dev" <foreman-dev@googlegroups.com>
> > Sent: Wednesday, December 11, 2013 1:54:05 PM
> > Subject: [foreman-dev] Auditing in Foreman
> >
> > I think for MDP3, we're thinking of adding in auditing. My question is
> > about
> > the audited gem. I've used audited in the past (when it was known as
> > acts_as_audited) and it was a solid gem. My concern though is that it's not
> > very well maintained (like they still haven't added Rails 4 support[1]).
> > I've also used the paper_trail gem[2] which I've had a lot of good
> > experiences with and it looks like it's a little bit better maintained. I'm
> > wondering if switching gems might be an option–assuming we could migrate
> > data over, etc. I bring this up now because I think it's worth addressing
> > before we integrate with Katello. Any thoughts would be appreciated.
Hi,
One problem with the Rails auditing gems in general is they are build around
ActiveRecord. That means you can't (at least without some hacks) use that
for tracking actions, that don't change the Rails app database (which is quite
common situation in Katello and probably Foreman as well).
I must be quite annoying with pointing so often to the Dynflow:) It's probably
because it was stated after two years of working on Katello and Foreman and
we tried to address our use cases in Katello and Foreman with it's architecture
as much as possible.
– Ivan
···
----- Original Message -----
> ----- Original Message -----
(hit send too soon)
I think this work would generally be for 1.4 or 1.5. Possibly 2.0 whenever we
decide to bump the major version.
