[FEATURE REQUEST] Mention whether minion is classic or onedir in salt versions report

[frebib]

Is your feature request related to a problem? Please describe.
Save @OrangeDog having to ask everyone whether their minion is onedir or not: #62951 (comment)

Describe the solution you'd like
salt-call -V to say whether the minion is onedir or not

Describe alternatives you've considered
N/A

[OrangeDog]

Haha, thanks.

It's in the Bug template but people often delete it without answering.
I also requested it here: #62589 (comment)

[darless]

This would only be useful for those on versions prior to 3006.

Does salt know itself whether it is onedir or not?

I installed both onedir and the classic model via the documentation provided in https://docs.saltproject.io/salt/install-guide/en/latest/topics/install-by-operating-system/ubuntu.html for 18.04 with salt-minion.

Below are the differences that could be used to flag that it is onedir or not.

• /usr/bin/salt-minion is a bash file in onedir mode, while in classic mode it is a python3 script.
• In classic mode the salt python package files are installed in /usr/lib/python3/dist-packages, in onedir they are not installed as it is a binary.
• In onedir mode the binary for saltstack is in /opt/saltstack/salt/run/run, in classic mode this directory doesn't exist.

From the items above: If saltstack uses a script that calls a binary then it's onedir otherwise it's classic.

[dfidler]

Legacy packages are going to be around for years. SUSE packages their own minions, and other legacy platform (not yet onedir), installation from source isn't going to be onedir, etc.

Even if it's not codified in salt --version(s) then it's worthwhile to at least have a documented method of determining if you're running a onedir/legacy/source-installed minion.