Bug #4734
closed
Provisioning templates should be seeded for every organization
Added by Ivan Necas over 10 years ago.
Updated over 6 years ago.
Description
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
- Assignee set to Ivan Necas
- Triaged set to No
- Triaged changed from No to Yes
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.
Thoughts?
That does have the advantage of making upgrades easier. We can update the templates without worrying a user has edited them. I don't see a Clone button at first glance, we'll probably need to add that.
- Bugzilla link set to 1116082
I submitted a PR to enable cloning in #1646. We also need to do #3103.
Do we really need to seed the template in each org? It'd be better if all read-only templates without taxonomy were available everywhere, should be possible with just a tweak to with_taxonomy_scope in Foreman. What do you think?
- Assignee changed from Ivan Necas to Justin Sherrill
- Translation missing: en.field_release set to 13
- Difficulty set to medium
- Has duplicate Bug #5618: Provisioning templates should be set for all locations in Fortello added
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/4450 added
- Target version changed from 49 to 54
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous