The AWS API Gateway HTTP APIs, a simplified version of the REST APIs, recently went GA and offer a lot of improvements over the current Lambda integration solution. With Terraform support for the new resource type, it’s time to see how it works and how simple it got to add an API to a Lambda function.

The more the better, of course, and with a password manager it’s trivially easy to generate and autofill a password of any length. But should that be something with hundreds of characters just to be sure, or is there a sensible lower limit to use as a rule of thumb?

For Bash scripts, almost everything is about side-effects. They typically work with system resources such as the network or the file system. Commands that behave differently based on external factors factors—like du or ls—have to be controlled by the test to ensure reproducibility. This post covers 3 alternatives to mocking: using aliases, functions, and PATH override. Live examples can be found in the testing-in-bash/mocking GitHub repo.

Unit testing in Bash is perhaps even more important than in most other languages. Because it has so many sharp edges it’s even more to benefit from a test suite during development. Although Bash comes with its own unique set of challenges when it comes to modularization, it’s possible to isolate and test individual components.