With several engineers and many Terraform Cloud workspaces, sprinkled with run triggers, it’s easy to overlook plans awaiting confirmation or forget about failed runs. While you can configure Slack notifications for failed runs, it quickly becomes noisy, raising alarm even if the problem is immediately mitigated.
I recently wanted to export issues of a few GitHub repositories and store them in Markdown files. I also liked additional data like state, labels and comments included in a nice format. So I made a script.
DNS records in AWS Route 53 does not support metadata, like tags or a description, to keep track of their use which is not always clear. I tried managing DNS records in bulk with Terraform variables and auto.tfvars files, but it quickly became messy. Terraform maps allow duplicate keys (but last definition wins) and the map is not (easily) sortable - so it’s hard to keep an overview.
It can be difficult to review pull requests on Flux CD Helm manifests that bump a chart version, slightly change the supplied values and other changes.
With my Flux Helm Diff GitHub Action, you can get the diff posted automatically as a comment on the PR, making reviews a lot smoother.
There are a few reasons why you may want to cache container images, when running workloads in AWS, e.g.:
When running tailscale up after rebooting my Ubuntu laptop acting as a subnet router, I would get this performance warning:
Warning: UDP GRO forwarding is suboptimally configured on wl0, UDP forwarding throughput capability will increase with a configuration change.
Following the recommendations didn’t seem to persist the suggested configuration changes after reboots though 🤔