Provisioning templates should be seeded for every organization
In previous version, the provisioning templates were marked to be shared across organizations, for simplicity reasons.
We probably want to keep orgs separated as possible, but we should prepare
independent set of provisioning templates then for provisioning of synced repos
to work out of the box
fixes #4734 - make katello templates available in all taxonomies
This change uses a new feature in foreman to mark templates as defaults
supplied by a third-party. We mark our templates as such, as well as
some Foreman templates we require.
The end result is that (a) these templates are made available in all
orgs and locations at creation, and (b) the templates can't be deleted
or modified, so we are free to update them at will. Users may clone a
template into their own org to customize it.
#5 Updated by Justin Sherrill about 8 years ago
I would argue that we should make our templates Read-only, and then add all the readonly templates to every org on creation. That way there is a single base template that all orgs share (that can't be edited), and every org can copy a template for their own use.