#2688 Adding CLI to obtain server/subsystem information
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by edewata.

Currently the systemctl status command provides a way to check the status of a Tomcat instance, but not individual PKI subsystem running in the instance. There's also a GetStatus servlet, but it's only used programmatically.

There should be an easier way to obtain basic server/subsystem information including the status and other relevant information using CLI. The CLI can be called manually by users or used programmatically too (e.g. in pkispawn). For example:

$ pki info
  Version: 10.4.5
  Subsystems: CA, KRA

$ pki ca-info
  Status: READY
  Archival mechanism: keywrap
  Wrapping key set: 0

$ pki kra-info
  Status: READY
  Archival mechanism: keywrap
  Recovery mechanism: keywrap

$ pki tks-info
  Status: UNAVAILABLE

The corresponding REST services already exist. Adding the CLI should be pretty straight forward.


Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

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

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)

3 years ago

Login to comment on this ticket.

Metadata