Archiving hammer-cli-foreman-ssh

Community
1

Hammer-cli-foreman-ssh plugin has been created a very long time ago, pre-REX time, to support running ssh commands on hosts. It works like this:

  1. User runs hammer host ssh command
  2. Hammer calls to Foreman for a host list
  3. Hammer initiates SSH connection to the hosts, from a local machine

That means proxy doesn’t make connection, a computer with Hammer does.

I believe this is directly against the philosophy of a Foreman/Proxy centric architecture of remote execution (as in REX plugin) and doesn’t make sense very much because the host running Hammer doesn’t even necessarily have connectivity to the hosts it tries to run commands on.

The plugin is not used in Satellite, has had the last functional commit at the beginning of 2015, and I am not aware of it being used by anyone in the community.

I am planning to archive the plugin unless someone objects soon. Is someone against it?

2

I know at least some community members for example @thomas-merz, so I would want to hear his opinion.

3

Thanks for thinking of me :slight_smile: But I really didn’t use hammer in the last months or even years. So from my side it can be archived. R.I.P. :headstone:

1 Like
4

Summarizing an offline conversation I had with @lhellebr.

It’s packaged for RPM (rubygem-hammer_cli_foreman_ssh) and Debian (jammy & bookworm). Then in the installer it’s also exposed (foreman::cli::ssh). Removing it for Foreman 5.0 is a good opportunity.

1 Like