Using 'changed by' in the audits tab

Hello,

Fantastic work on 0.1.5 btw, much improved!

I'm curious about the 'Changed By' column in the audits tab. It would
be great to keep track of who pushed a particular configuration change
for auditing later. Is that was this is intended for? How would one
gather that information for foreman?

Currently, I have puppet configurations living in an svn repo and
people commit to that repo as unique uids. Is that enough?

Thanks for your help!

–Ryan

Hi Ryan,

The audit trail log checks for any modifications to Foreman's db, e.g. when
a host property changes (e.g. ip address, parameter or class assignment).
some of the changes are done automatically (e.g. when a fact changes), but
for those ones which are done by a user, we can keep the user id (assuming
you are using authentication within foreman).

at the moment, there are no plans (read = i have no idea of how) to
integrate your repository and foreman - any ideas are welcomed!

Cheers,
Ohad

··· On Wed, Jun 9, 2010 at 10:23 PM, Ryan wrote:

Hello,

Fantastic work on 0.1.5 btw, much improved!

I’m curious about the ‘Changed By’ column in the audits tab. It would
be great to keep track of who pushed a particular configuration change
for auditing later. Is that was this is intended for? How would one
gather that information for foreman?

Currently, I have puppet configurations living in an svn repo and
people commit to that repo as unique uids. Is that enough?

Thanks for your help!

–Ryan


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.comforeman-users%2Bunsubscribe@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

Perhaps the class import code could be taught to check if the modules dir is
part of a repo of some flavor, and if so, also suck in the changelog?

··· On 6/10/2010 12:13 AM, Ohad Levy wrote: > Hi Ryan, > > The audit trail log checks for any modifications to Foreman's db, e.g. > when a host property changes (e.g. ip address, parameter or class > assignment). > some of the changes are done automatically (e.g. when a fact changes), > but for those ones which are done by a user, we can keep the user id > (assuming you are using authentication within foreman). > > at the moment, there are no plans (read = i have no idea of how) to > integrate your repository and foreman - any ideas are welcomed!


Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC