Weekly Newsletter
#
4
Delivery pipeline as legacy code, YAML proliferation, readable git logs, and more
More Facebook data leaks, more misconfigured S3 buckets. Should AWS start forcing people to jump through hoops before they can make buckets public? 🤔 If you missed it last week, our very own Eyar Zilberman wrote an awesome guide to git commit message convention. This is how you can have nice things like readable git logs. RegEx cheatsheet included.
Highly effective Kubernetes deployments with GitOps
The benefits of GitOps approach to Kubernetes deployments are that it enables easy recovery from disaster, provides a simple and well understood operational model, and better security and audit trail.
The anatomy of an AWS key leak to a public code repository
Maish Saidel-Keesing breaks down what happens in an incident involving a leaked secret, including the actual email alerts from AWS, how long it took them to arrive, and what he did next.
When YAML breeds: Distributed Denial of Productivity
As YAML files proliferate, the problem of inconsistencies & duplications grows. Rod Johnson finds in Github's 90 repos there are 40 different Travis script stanzas; some don't even use npm; some reporting test coverage one way, others another way, most not at all...
How I'm still not using GUIs in 2019 - a guide to the Terminal
An opinionated post by Lucas Costa about why he likes using terminal and his terminal setup. Yes, he uses Vim ✌️
Your delivery pipeline will be your next big legacy code challenge
Alois Reitbauer explains: "Build scripts are now code. Jenkins pipelines are code. Infrastructure provisioning is code... we now create a lot of code around our app source code that doesn't have the same requirements for testing, documentation, and long-term maintainability."