Project

General

Profile

Feature #11634

Allow job execution with ssh user set to different user (e.g. cloud-user) per host

Added by Stephen Benjamin almost 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-

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.


Related issues

Related to Foreman Remote Execution - Bug #12313: smart proxy ssh user not usedClosed2015-10-26

Associated revisions

Revision 360eb185 (diff)
Added by Stephen Benjamin almost 7 years ago

refs #11634 - use ssh_user from task input

Revision 8947c1cd (diff)
Added by Stephen Benjamin almost 7 years ago

fixes #11634 - allow customization of ssh user

Revision 69e5ec00
Added by Stephen Benjamin almost 7 years ago

Merge pull request #10 from stbenjam/11634

refs #11634 - use ssh_user from task input

Revision 80e5b4ce
Added by Stephen Benjamin almost 7 years ago

Merge pull request #69 from stbenjam/11634

fixes #11634 - allow customization of ssh user

History

#1 Updated by Ivan Necas almost 7 years ago

  • Target version set to 87

#2 Updated by Stephen Benjamin almost 7 years ago

  • 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?

#3 Updated by Stephen Benjamin almost 7 years ago

  • Assignee set to Stephen Benjamin

#4 Updated by The Foreman Bot almost 7 years ago

  • 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 ()

#5 Updated by Stephen Benjamin almost 7 years ago

  • Related to Bug #12313: smart proxy ssh user not used added

#6 Updated by The Foreman Bot almost 7 years ago

  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/69 added

#7 Updated by Anonymous almost 7 years ago

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

#8 Updated by Stephen Benjamin almost 7 years ago

  • Legacy Backlogs Release (now unused) set to 103

Also available in: Atom PDF