Best practice for maintaing templates

I am new Foreman and have a very delicately put together template for some
of my machines. What's the best way to maintain this information in source
control? Is it possible to have the template be simply symbolically linked
from within a git repo and be displayed properly by Foreman?

Hello,

unfortunately templates are stored in the SQL database and currently
there is no way to integrate them with SCM AFAIK.

On the other hand, Foreman does support organizations, users,
permissions and it has strong auditing subsystem. Also, when you make a
change in a template, Foreman is able to show you differences and
you can track history of template changes. I think currently you can't
go back (revert).

LZ

··· On Mon, Mar 25, 2013 at 04:59:30PM -0700, Stephen Wood wrote: > I am new Foreman and have a very delicately put together template for some > of my machines. What's the best way to maintain this information in source > control? Is it possible to have the template be simply symbolically linked > from within a git repo and be displayed properly by Foreman? > > -- > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > >


Later,

Lukas “lzap” Zapletal
#katello #systemengine

It does have a form of internal SCM, combined with the audit system. If you
go to a template and click the history tab, you'll be able to review all
the diffs of the changes to that template. Coupled with the audits of who
changed the template, it's fairly robust.

If you absolutely must dump to a flat file, you can probably craft a shell
script that uses (mysql|psql|sqlite) to dump the relevant tables to files.

Greg

··· On 26 March 2013 09:17, Lukas Zapletal wrote:

Hello,

unfortunately templates are stored in the SQL database and currently
there is no way to integrate them with SCM AFAIK.

>
>> Hello,
>>
>> unfortunately templates are stored in the SQL database and currently
>> there is no way to integrate them with SCM AFAIK.
>>
>
> It does have a form of internal SCM, combined with the audit system. If
> you go to a template and click the history tab, you'll be able to review
> all the diffs of the changes to that template. Coupled with the audits of
> who changed the template, it's fairly robust.
>
> If you absolutely must dump to a flat file, you can probably craft a shell
> script that uses (mysql|psql|sqlite) to dump the relevant tables to files.
>
>
I would love a git plugin to foreman, it should not be too hard to
implement imho.

another option, would be create a simple git post hook which would use the
API to upload the template.

Ohad

Greg

··· On Tue, Mar 26, 2013 at 12:09 PM, Greg Sutcliffe wrote: > On 26 March 2013 09:17, Lukas Zapletal wrote: > > -- > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > >