Open renanrodrigo opened 7 months ago
A specific mapping would be nice, if possible, for example pointing people using pro system reboot-required
to https://canonical-ubuntu-pro-client.readthedocs-hosted.com/en/latest/references/api/#u-pro-security-status-reboot-required-v1 rather than just a generic warning.
Will do our best to solve this as part of the current UX redesign - if it is not there immediately, then we can do it at some future iteration
Please describe the scenario where the new feature would be useful
We currently have a warning printed to
stderr
when running a command that is supposed to be human readable on scripts (actually, anywhere but a TTY). Those are implemented based on the """old"""--format json|yaml
machine readable formats. The coverage is only status and security-status. We could instead put this warning anywhere but the API - so people consuming from Pro at least get a hint that they should not automate things based on human-readable output.Describe the solution you'd like
Exactly what is implemented now for
pro status
andpro security-status
, but for all commands that are supposed to present human readable output.Current behavior
As described, only
status
andsecurity-status
have this implemented.Additional context
This request reached us during the UX review process, and was considered good enough to justify this issue for the future. Tackling this one can wait until the new UX is actually implemented.