Feature #11634
closed
Allow job execution with ssh user set to different user (e.g. cloud-user) per host
Added by Stephen Benjamin about 9 years ago.
Updated over 6 years ago.
Description
For image-based hosts, Foreman stores a username, like "cloud-user" or "fedora", we could rely on that. For bare metal, we might need to allow customizing it per-host somehow. Development machines might allow raw ssh as root, production machines might be more restricted.
- Subject changed from Allow job execution with effective user set to different user (e.g. cloud-user) per host to Allow job execution with ssh user set to different user (e.g. cloud-user) per host
Sorry that should be ssh user, not effective user. I also noticed the smart proxy :ssh_user: setting is currently unused - maybe it's best if we let foreman control it in the task input?
- Assignee set to Stephen Benjamin
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/10 added
- Pull request deleted (
- Related to Bug #12313: smart proxy ssh user not used added
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/69 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 103
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous