As a user, I can machine-parse pulp-admin output
I don't think that this is unique to pulp-admin, but my report is specifically for that. Anyway, pulp-admin automatically linewraps output, which is pretty, but makes it difficult to parse and make use of the data that it outputs since it's often truncated and completed on multiple lines. Since we use excessively long labels by default, it makes it quite difficult to work with:
[root@garabaldi pulp]# pulp-admin repo list --details | head
Display Name: Red Hat Enterprise Linux 6 Server - Extras RPMs x86_64
Content Unit Counts:
SSL CA Cert: -----BEGIN CERTIFICATE-----
This makes human parsing a bit challenging at times and makes automatic parsing of the output quite difficult. It also breaks format of SSL CA Cert keys.
One can work around this in an ugly way by specifying:
wrap_to_terminal = false
wrap_width = <some arbitrary long value longer than the longest field>
...which is unappealing, and also has us create really, really long dividers and the like in our attempt to prettify the output. I put a hack in to limit the dividers to 80 characters, but that's not really a fix. It'd be nice if we could just disable line-wrapping as an option here.
Version-Release number of selected component (if applicable):
#5 Updated by rbarlow almost 4 years ago
- Tracker changed from Story to Issue
- Severity set to 2. Medium
- Triaged set to No
I think this should be an issue instead of a story, especially since it is making pulp-smash especially difficult to work on. I think we should consider raising the priority considering pulp-smash and that it has now been reported three times.
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue