Production is hard. Even a simple script that looks up queue state and sends it to an API gets complex in prod. Without tests, the divide by zero case you missed will mask queue overloads. Someone won’t see that required argument you didn’t enforce and break everything when they accidentally publish a null value. You’ll forget to timestamp one of your output lines and then when the queue goes down you won’t be able to correlate queue status to network events.
Python can help! Out of box it can give you essential but often-skipped features, like these:
- Automated tests for multiple platforms.
- Command line sanity like a
--helpoption and enforcement of required arguments.
- Informative log output.
- An easy way to build and package.
- An easy way to install a build without a git clone.
- A command that you can just run like any other command. No weird shell setup or invocation required.
It can be a little tricky, though, if you haven’t already done it. So I wrote a project that demonstrates it for you. It includes an example of a script that isn’t ready for prod.
Hopefully this will save you from some of the many totally avoidable, horrible problems that bad scripts have caused in my prods.
Thanks for reading!
If this was helpful and you want to save time by getting “copy and paste” patterns for Cloud DevOps in your inbox, subscribe here.