Feature #12489
closed
Expose effective user in the foreman server
Added by Ivan Necas about 9 years ago.
Updated over 6 years ago.
Description
As an Foreman user, I want to be able to determine what effective user should be used for the
execution, based on host params. The effective user is enforced by using su/sudo on the managed host.
- Status changed from New to Assigned
- Assignee set to Ivan Necas
I was wondering if it shouldn't be at the invocation level? My thinking was maybe a job to perform some postgresql maintenance would be run under postgres, but another job to install some packages would be root.
Definitely the job template needs to have the last word on the strategy, but multiple strategies will need to be in place.
I was thinking about an erb template for this value, quite smilar to other input types.
Ah I see, that sounds good then
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/16 added
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/80 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/83 added
- Translation missing: en.field_release set to 108
- Has duplicate Feature #13184: Remote Execution needs ability to restrict commands on a per user basis added
Also available in: Atom
PDF