allow fingerprinting of classic cpu architecture names

[shantanugadgil]

Proposal

Currently the cpu is fingerprinted using the GOARCH (amd64, arm64).

Sometimes we need the "traditional" name of the CPU architecture; i386, x86_64, etc.

This proposal is to allow the Nomad agent to fingerprint the "classic" name for the CPU architecture.

Use-cases

Software which ship using the classic CPU architecture in their filenames cannot be downloaded using the "inbuilt" variable ${attr.cpu.arch}.

We need to write custom script (?) code to use aarch64, x86_64 in the download file name depending on amd64, arm64.

Attempted Solutions

Currently making do using a custom script and leveraging if/else using the output of uname -m

Please note: the name "classic" is what popped into my mind, I am open to any other named being used for this as well.

[lgfa29]

Closed by #13182

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.