Description of problem: Currently hammer cli cannot clone config_templates with a sub-command. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. "hammer template" has no "clone" sub-command. 2. 3. Actual results: No "clone" sub-command, for "hammer template". Expected results: "hammer template" needs to have a "clone" sub-command. Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/13946 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/13946 has been closed ------------- Shimon Shtein Applied in changeset commit:hammer-cli-foreman|5aaa69fa1f9df50480002d92c9f42c5ede1b9635.
We now have "clone" sub_command, [root@xyz ~]# hammer -u admin -p changeme template --help Usage: hammer template [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND subcommand [ARG] ... subcommand arguments Subcommands: add-operatingsystem Associate an operating system build-pxe-default Update the default PXE menu on all configured TFTP servers clone Clone a provision template create Create a provisioning template delete Delete a provisioning template dump View config template content. info Show provisioning template details kinds List available config template kinds. list List provisioning templates remove-operatingsystem Disassociate an operating system update Update a provisioning template Options: -h, --help print help [root@xyz ~]# hammer -u admin -p changeme template clone --help Usage: hammer template clone [OPTIONS] Options: --id ID --name NAME Name to search by --new-name NEW_NAME template name -h, --help print help VERIFIED with sat62-snap12.1
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. https://access.redhat.com/errata/RHBA-2016:1501