Plugins » Katello

Anyway I'd like to implement possibility to change hardcoded template names in Settings. I wish I remember how to change issue subject in RedMine :-(

Lukas Zapletal wrote:

Anyway I'd like to implement possibility to change hardcoded template names in Settings.

#7484 covers the subnet bit, you could file another ticket for that if you wish.

I wish I remember how to change issue subject in RedMine :-(

Click Edit, click pencil icon next to Description.

Please keep this one to fix the locking of Foreman's templates.

Katello should not be locking core Foreman templates: https://github.com/Katello/katello/blob/katello-2.0.0-0/db/seeds.rb#L39-L44

I disagree. Foreman should be locking core templates, so that you can update them at will, but you're stuck due to precedence.

In a multi-org and multi-loc setup, having the core templates editable is just totally broken.

Just some more background, I originally tried the permissions model, but you may have a user who should be able to change associations (requiring 'edit' permission) but not the template content.

Fire up Katello and try to imagine managing a multi-org setup with users with varying levels of permissions, with the default templates unlocked. You're opening yourself up to pure chaos when a user in Org A with no permissions to Org B are able to change a template they rely on. The core templates need to be locked for Katello to work sensibly.

I'm open to a suggestion that could fix this, and perfectly happy if you can find one in Foreman itself.

(Although the issue at hand is fixed by not hard coding template names in the code, and the Katello locked templates issue should be done elsewhere, feel free to file an issue about it)

To work around this for 2.0:

echo ConfigTemplate.find_by_name('PXELinux global default').update_attribute(:locked, false) | foreman-rake console

This allows the user to unlock the template. I believe the longer term solution is to make this not hardcoded in foreman.