eyJhb: Why do people see the need to hardcode paths to bins? https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/blob/master/smartmon.sh#L186
This is one of the reasons resholve treats existing absolute executable paths as an error unless you intentionally exempt them:
$ resholve --interpreter none --path $PATH smartmon.sh
smartctl_version="$(/usr/sbin/smartctl -V | head -n1 | awk '$1 == "smartctl" {print $2}')"
^~~~~~~~~~~~~~~~~~
/Users/abathur/work/resholved/smartmon.sh:165: Unexpected absolute command path (not supplied by a listed dependency). You should patch/substitute it.
You can also tell resholve to resolve such a path from inputs:
$ resholve --interpreter none --path $PATH --fix /usr/sbin/smartctl smartmon.sh
smartctl_version="$(/usr/sbin/smartctl -V | head -n1 | awk '$1 == "smartctl" {print $2}')"
^~~~~~~~~~~~~~~~~~
/Users/abathur/work/resholved/smartmon.sh:165: Can't resolve command 'smartctl' to a known function or executable
(this would work if I had smartmontools in my inputs/path)