On 09/29/2017 11:23 AM, Sean A wrote:
Hi,
I have an idea to improve(?) the provision templates delivered with
Foreman.
Over time, I've struggled to merge/rebase updates that are put into the
core templates into the "clones" that I have implemented for our system
profiles. Would it be possible to add a method (snippet or array
parameter) to allow for setting additional packages/package groups to be
installed at provision time? This would hit 95% of the reason we clone
provision templates to fulfill provisioning of systems with different
profiles...and allow end-users like me the ease of not having to rebase
template clones after every template update.
We use provision templates for both servers and desktops, the desktops
deliver over 1300 packages during provisioning, and I'm loathe to try
and manage that much directly with Puppet post install.
If this is off topic, should I just take this over to the
community-templates repo on github for further discussion?
I think it would be very interesting to have this extended to eh
hostgroup form.
-- b
k
--
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.
