In fact anything that triggers foreman-rake db:seed changes the default template content (Foreman 1.14+). That can be run of foreman-installer, installing a plugin or manual trigger. These changes are not audited IIRC. If you need to adjust template that is shipped by default, it is a good idea to clone it first. Note that you'd miss all future updates and it's up to you to keep it up to date. Default templates should be locked since 1.15.
-- Marek On úterý 26. září 2017 13:24:21 CEST Greg Sutcliffe wrote: > On Tue, 2017-09-26 at 13:51 +0300, Ido Kaplan wrote: > > Hi Greg, > > > > I mean about contents of the templates in Foreman, for example - > > "Kickstart default.rb"? > > Those should not be altered by that button, no. The only time the > default templates would be updated would be during a version upgrade of > Foreman. > > Changes to templates are audited, so you should be able to see the > history of changes, so that's worth looking at to see what might have > made the changes. Also, if you can reproduce it reliably, we can try > and see if we see the same behaviour > > Greg -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
