#2537 Renaming pki --output parameter
Closed: migrated by dmoluguw. Opened by edewata.

The pki CLI provides a --output parameter to store the HTTP requests and responses in the specified folder. The parameter name is a bit too generic and it might be confused with other --output parameters used by pki subcommands, so it should be renamed into something like --store-messages or --http-message-dir.


Per PKI Bug Council of 11/10/2016: 10.4 - minor

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1394070

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

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.4 (was: UNTRIAGED)

Metadata Update from @edewata:
- Issue set to the milestone: FUTURE (was: 10.4)

Metadata Update from @mharmsen:
- Custom field lowhangingfruit adjusted to vakwetu: X

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1394070)

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/2657

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

Metadata