Project

General

Profile

Bug #9245

Add override setting to allow mcollective puppet runs to run as a different user

Added by Corey Osman almost 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet
Target version:
Difficulty:
trivial
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

This is similar to #3150 with the exception that since the puppet_user setting is used in other places we may want to allow one to override the setting.

The generic name of puppet_user in the settings file doesn't really detail what its used for. By adding a new user type it should be pretty explicit what user
is going to be used for mcollective puppet runs.

Associated revisions

Revision 75f58711 (diff)
Added by Corey Osman almost 6 years ago

Fixes #9245 - Add override setting to allow mcollective puppet runs to run as a different user

  • previously we could set the mcollective user via puppet_user setting. However, this could be misleading
    to the user as its not obvious where it was used in the smart proxy. With the new mcollective user
    setting its pretty clear what the intention of the user is for. In setups like Puppet Enterprise
    there is usually a user for mco and puppet which we have to keep separate and thus require a different user.
  • This adds a new setting to the puppet config called :mcollective_user:

History

#1 Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/255 added
  • Pull request deleted ()

#2 Updated by Corey Osman almost 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Dominic Cleal over 5 years ago

  • Legacy Backlogs Release (now unused) set to 28

Also available in: Atom PDF