| ▲ | ffsm8 4 hours ago | |||||||
The issue with solutions like that is usually that people don't know how it works and how to find it if it ever stops working... Basically discoverability is where shell script fail | ||||||||
| ▲ | roncesvalles 19 minutes ago | parent | next [-] | |||||||
You can literally have a 20 line Python script on cron that verifies if everything ran properly and fires off a PagerDuty if it didn't. And it looks like PagerDuty even supports heartbeat so that means even if your Python script failed, you could get alerted. | ||||||||
| ▲ | chuckadams 4 hours ago | parent | prev | next [-] | |||||||
Those scripts have logs, right? Log a hostname and path when they run. If no one thinks to look at logs, then there's a bigger problem going on than a one-off script. | ||||||||
| ▲ | LevGoldstein 2 hours ago | parent | prev | next [-] | |||||||
Which is why you take the time to put usage docs in the repo README, make sure the script is packaged and deployed via the same methods that the rest of the company uses, and ensure that it logs success/failure conditions. That's been pretty standard at every organization I've been at my entire professional career. Anyone who can't manage that is going to create worse problems when designing/building/maintaining a more complex system. | ||||||||
| ||||||||
| ▲ | woooooo 4 hours ago | parent | prev | next [-] | |||||||
That becomes a problem if you let the shell script mutate into an "everything" script that's solving tons of business problems. Or if you're reinventing kubernetes with shell scripts. There's still a place for simple solutions to simple problems. | ||||||||
| ▲ | justsomehnguy 4 hours ago | parent | prev [-] | |||||||
> Basically discoverability is where shell script fail No, it's lack of documentation and no amount of $$$$/m enterprise AI solutions (R)(TM) would help you if there is no documentation. | ||||||||