Not the point. It doesn’t, mine does, and that’s the reason for the additional Python dependency of my script. This was not a criticism of truenas_ws.sh; it was simply an observation of a difference.
And I think this is the fundamental problem–you’re assuming things rather than taking even the slightest effort to ascertain the facts. A moment of reviewing the README, the link to which was in my first post in this thread, would have cleared this up for you. Your assumption is correct, but your lack of effort to confirm it is telling.
Your comments in the other thread,[1] where you repeatedly advised against using Python despite one script being completed, and another mostly so, in that language, paint a different picture.
It was indeed. I didn’t suggest, and don’t believe, that you wrote it, but if you’d compared the code enough to form the opinion that the one was better, I’d expect you to have recognized it.
That was your claim, not mine. I’ll happily consider PRs, and willingly look into any specific issues you (or anyone else) note. As far as I can tell–and I’ll freely admit I’m no expert in Python–the code is pretty straightforward. Error handling could no doubt still be improved. As for other issues, as I said, I’m open to suggestions.
No, but it’s kind of frustrating when you drop into a thread to post something that isn’t really relevant to it, as you did here. The truenas_ws.sh script just isn’t relevant to OP’s question:
- It can’t be used on a different system than the NAS to deploy a cert to the NAS (the
truenas.shscript can, but thetruenas_ws.shscript can’t), which is how OP is currently handling the cert (though deploying it manually), and - There’s simply no need for it if you’re getting a cert through the NAS interface (which is what OP asked about).
…and when you double and triple down on your incorrect claim that the link you give documents how to use truenas_ws.sh, well…