We use puppet node definitions, handled via subversion, but are looking at
moving to foreman as an ENC. Today, when committing changes to a node, we
put the ID number of the issue from our issue tracker in the subversion
comment for the change. This makes it easy for us to track changes by using
'svn log' to find the issue ID for a specific change and then check our
issue tracking system for more info.
Foreman has its auditing system and i like it, but it does not provide the
possibility to add a comment to a change, to for exampel add a issue
tracking ID which contains more info about the change and who ordered it.
Have anyone out there faced this problem and how do you work around it?
Thanks,
Adam
> We use puppet node definitions, handled via subversion, but are looking at
> moving to foreman as an ENC. Today, when committing changes to a node, we
> put the ID number of the issue from our issue tracker in the subversion
> comment for the change. This makes it easy for us to track changes by using
> 'svn log' to find the issue ID for a specific change and then check our
> issue tracking system for more info.
>
> Foreman has its auditing system and i like it, but it does not provide the
> possibility to add a comment to a change, to for exampel add a issue
> tracking ID which contains more info about the change and who ordered it.
> Have anyone out there faced this problem and how do you work around it?
>
> We actually offer audit custom message for some actions (e.g. when you
change a provisioning template), I Assume a feature request to add similar
functionality to other parts in the applications make sense as well?
thanks!
Ohad
···
On Wed, Sep 25, 2013 at 9:22 AM, AdamW wrote:
Thanks,
Adam
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
oh, missed that since i dont use that feature, but that looks like what im
looking for. It would be great to have in other parts as well, would also
be great if you could make this audit message mandatory (maybe not by
default though, but optional), and accessible from the API.
/Adam
···
On 25 September 2013 08:24, Ohad Levy wrote:
On Wed, Sep 25, 2013 at 9:22 AM, AdamW adam.winberg@gmail.com wrote:
We use puppet node definitions, handled via subversion, but are looking
at moving to foreman as an ENC. Today, when committing changes to a node,
we put the ID number of the issue from our issue tracker in the subversion
comment for the change. This makes it easy for us to track changes by using
’svn log’ to find the issue ID for a specific change and then check our
issue tracking system for more info.
Foreman has its auditing system and i like it, but it does not provide
the possibility to add a comment to a change, to for exampel add a issue
tracking ID which contains more info about the change and who ordered it.
Have anyone out there faced this problem and how do you work around it?
We actually offer audit custom message for some actions (e.g. when you
change a provisioning template), I Assume a feature request to add similar
functionality to other parts in the applications make sense as well?
thanks!
Ohad
Thanks,
Adam
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
would you mind adding feature requests to the tracker? thanks!
···
On Wed, Sep 25, 2013 at 9:36 AM, Adam Winberg wrote:
oh, missed that since i dont use that feature, but that looks like what im
looking for. It would be great to have in other parts as well, would also
be great if you could make this audit message mandatory (maybe not by
default though, but optional), and accessible from the API.
/Adam
On 25 September 2013 08:24, Ohad Levy ohadlevy@gmail.com wrote:
On Wed, Sep 25, 2013 at 9:22 AM, AdamW adam.winberg@gmail.com wrote:
We use puppet node definitions, handled via subversion, but are looking
at moving to foreman as an ENC. Today, when committing changes to a node,
we put the ID number of the issue from our issue tracker in the subversion
comment for the change. This makes it easy for us to track changes by using
’svn log’ to find the issue ID for a specific change and then check our
issue tracking system for more info.
Foreman has its auditing system and i like it, but it does not provide
the possibility to add a comment to a change, to for exampel add a issue
tracking ID which contains more info about the change and who ordered it.
Have anyone out there faced this problem and how do you work around it?
We actually offer audit custom message for some actions (e.g. when you
change a provisioning template), I Assume a feature request to add similar
functionality to other parts in the applications make sense as well?
thanks!
Ohad
Thanks,
Adam
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.
