Actions
Feature #12489
closed
Expose effective user in the foreman server
Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
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.
Updated by Ivan Necas about 9 years ago
- Status changed from New to Assigned
- Assignee set to Ivan Necas
Updated by Stephen Benjamin about 9 years ago
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.
Updated by Ivan Necas about 9 years ago
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.
Updated by The Foreman Bot almost 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/16 added
Updated by The Foreman Bot almost 9 years ago
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/80 added
Updated by Ivan Necas almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_plugin|7c949a4da8cd5236b64dda7df3304de9b41b2aa9.
Updated by The Foreman Bot almost 9 years ago
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/83 added
Updated by Marek Hulán almost 9 years ago
- Translation missing: en.field_release set to 108
Updated by Stephen Benjamin almost 9 years ago
- Has duplicate Feature #13184: Remote Execution needs ability to restrict commands on a per user basis added
Actions