Feature: Simplify obtention of client debug information via the CLI

[alnvdl-work]

Please describe the scenario where the new feature would be useful We often get requests from users and have a hard time figuring out what account or product they are using. We often instruct them to give us the output of pro status --format=json, which contains all the information, but is a bit hard to read (and some users may be uncomfortable sharing all that information).

In more uncommon cases, we may have to help users identify machines in their fleet, and currently we tell them to look at /etc/machine-id for this purpose, which is a good but not a perfect proxy for the machine ID.

Describe the solution you'd like There are 6 bits of information that are useful for quickly debugging issues in the backend:

• Pro account ID
• Pro token ID (a.k.a., contract ID)
• Machine ID
• Activity ID
• Enabled resources (including non-vanilla resources)
• Series

This could be printed in the output of the CLI when running something like pro support-info or pro status --support-info. I'm not an expert in coming up with names for Pro commands, but I know you have the world's foremost expert in that field working for your team :smile:

Current behavior Some of the information above is partially available through pro status --format=json and in /etc/machine-id.

[renanrodrigo]

@alnvdl-work one thing that comes to mind - what exactly are you calling "vanilla" resources in this context?

[alnvdl-work]

@alnvdl-work one thing that comes to mind - what exactly are you calling "vanilla" resources in this context?

@renanrodrigo By non-vanilla I mean resources that are enabled but not visible when you run pro status.