This was a nice to have feature for our latest epic on information gathering. It's about being as transparent as possible to users as to what kind of information is being gathered by SUSEConnect. This is already available with the --debug flag on, but this is a more user-friendly approach.
How
The PR simply exports the FetchSystemInformation function and uses it. The output is always in JSON because it is more transparent to also show this in the format it's delivered/used in the end.
How to test
Simply running with suseconnect --info or suseconnect -i, and you should get a proper output. Pair it with jq and you'd get an extra dope output.
Why
This was a nice to have feature for our latest epic on information gathering. It's about being as transparent as possible to users as to what kind of information is being gathered by SUSEConnect. This is already available with the
--debugflag on, but this is a more user-friendly approach.How
The PR simply exports the
FetchSystemInformationfunction and uses it. The output is always in JSON because it is more transparent to also show this in the format it's delivered/used in the end.How to test
Simply running with
suseconnect --infoorsuseconnect -i, and you should get a proper output. Pair it withjqand you'd get an extra dope output.