tps-profile-mod cli utility shows extra options which it doesn't support
example:
pki -d /tmp/testing -c Secret123 -h `hostname` -p 12080 -n "PKI Administrator - os1.phx2.redhat.com Security Domain #2" tps-profile-mod soCleanUserToken Error: Missing input file usage: tps-profile-mod <Profile ID> [OPTIONS...] --action <action> Action: update (default), submit, cancel, approve, reject, enable, disable. --help Show help options --input <file> Input file containing profile properties.
So, this cli shows it supports update,submit,cancel,approve,reject But when we try out other options none of them works . Only "Enable" and "Disable" options works .
pki -d /tmp/testing -c Secret123 -h `hostname` -p 12080 -n "PKI Administrator - os1.phx2.redhat.com Security Domain #2" tps-profile-mod soCleanUserToken --action reject BadRequestException: Invalid action: reject
Steps to Reproduce:
Refer to the description section.
Actual results:
Currently cli allows man actions like update (default), submit, cancel, approve but none of them work.Only Enable and disable work
Expected results:
Cli should have only supported actions. Either we should support all the above mentioned or remove them.
Per CS/DS Meeting of 02/15/2016: 10.3 - minor
Per CS Bug/Ticket Triage held 04/19/2016: 10.3.1
We at least need to chance the usage message if we don't make the tool support all actions.
Per PKI Bug Council of 06/23/2016: 10.3.4
Per CS/DS Meeting of 08/08/2016: 10.3.6
NOTE: It is believed that this ticket may be a man page change.
Per discussions in PKI Bug Council of 01/19/2017 it was determined that this ticket would not be addressed until Dogtag 10.4.
Metadata Update from @gkapoor: - Issue assigned to edewata - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: critical (was: minor)
Metadata Update from @mharmsen: - Issue priority set to: minor (was: critical)
Metadata Update from @mharmsen: - Issue priority set to: major (was: minor)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.5.x
edewata: misleading help/error message
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2321
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)