Project

General

Profile

Feature #2297

Ability for admins to lock certain templates, hostgroups, and disk layouts from editing

Added by Jason Montleon over 7 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

I'm setting up a server for use by multiple organizations.

I'd like to provide them with access to some base working kickstarts, snippets, pxe templates, disk layouts, and hostgroups to get them started.

At the same time I am expecting at least some people will want to create, edit, and delete templates, but I fully expect that if I give full access someone is going to break one of the ones shared to all.

So my options seem to be either revoking at least edit/delete which makes create less appealing as well or making 13 copies of each (13 orgs times 8 templates/layouts off the top of my head) template, disk layout, and hostgroup we use for each org, so they will only harm their own org if they break something.

Neither seems like a very good approach.


Related issues

Related to Foreman - Tracker #6631: Provisioning Template ImprovementsNew2014-07-16

Related to Foreman - Feature #1646: Add feature to clone provisioning templatesClosed2012-05-22
Related to Foreman - Feature #3103: Read only provisioning/config templates for pluginsClosed2013-09-17

History

#1 Updated by Ohad Levy over 7 years ago

I would assume is relevant to parameters? (class vars, smart vars etc)

#2 Updated by Jason Montleon over 7 years ago

It might be helpful to be able to lock them as well, but I don't think I'm as immediately concerned about them. Sam mentioned the idea of an acl system as well, which would be great. But I would settle for being able to lock certain ones down.

#3 Updated by Stephen Benjamin about 6 years ago

  • Related to Tracker #6631: Provisioning Template Improvements added

#4 Updated by Stephen Benjamin about 6 years ago

  • Related to Feature #1646: Add feature to clone provisioning templates added

#5 Updated by Stephen Benjamin about 6 years ago

  • Related to Feature #3103: Read only provisioning/config templates for plugins added

#6 Updated by Marek Hulán over 3 years ago

  • Description updated (diff)
  • Status changed from New to Resolved

I think one can achieve all of that already with granular permission system and in case of partition tables and provisioning templates, one could even use the locking mechanism. Please let me know if I misunderstood the request, I'd reopen the issue.

Also available in: Atom PDF