Red Hat Bugzilla – Bug 1476224
Creating SSH Key in User Template functionality missing in hammer CLI
Last modified: 2018-02-21 12:03:56 EST
Description of problem:
Creating/Deleting/Viewing/Listing SSH Key in user template functionality is completely missing from hammer CLI
Version-Release number of selected component (if applicable):
Satellite 6.3 Snap 7
Steps to Reproduce:
1. Create User with required details
2. From Hammer, Attempt to add ssh key in above user
No provision to create/delete/view/list the ssh keys from CLI hammer in user template
Hammer CLI should have provision to create/view/list/delete the ssh key in user template
Functionality is available from API
Created redmine issue http://projects.theforeman.org/issues/20476 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20476 has been resolved.
Satellite 6.3.0 snap 18.0
I don't see any ssh-key option either in:
-> hammer user
-> hammer user create
-> hammer user update
-> hammer ssh-key
So, failing this bug.
Upstream bug assigned to email@example.com
Upstream bug assigned to firstname.lastname@example.org
@ Satellite 6.3 snap 25
Commands are available to add, delete, info and list the ssh-key:
# hammer user ssh-keys --help
hammer user ssh-keys [OPTIONS] SUBCOMMAND [ARG] ...
[ARG] ... subcommand arguments
add Create an SSH key for a user
delete Delete an SSH key for a user
info Show an SSH key from a user
list List all SSH keys for a user
-h, --help print help
Each option is tested thoroughly and all works nicely.
The only gap I see in CLI compare to UI is,
While creating an ssh-key in user UI automatically populates the ssh-key name from ssh-key. But CLI hammer doesn't and asks for name compulsory. It would be nice to drag that functionality from UI to CLI.
But anyhow that doesn't block this bug from verification.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.