Tools Folder | Platform

Now, even the most stressed engineer during an incident can run:

April 14, 2026 Reading Time: 4 minutes

# Platform Makefile .PHONY: tools/% tools/%: @echo "🔧 Running platform tool: $ " @./tools/$ clean-volumes: tools/clean-orphaned-volumes db-failover: tools/db-failover platform tools folder

Platform engineering is not about building more abstractions. It is about reducing toil. And nothing reduces toil like a folder full of buttons (that you can git grep ).

We moved it all to tools/monday-cleanup . Now, the on-call engineer runs: Now, even the most stressed engineer during an

You have three different scripts to clean up AWS resources. Your on-call engineer is running a Python snippet from a forgotten Gist. And your "golden path" documentation is already two major versions behind the actual CLI tooling.

# tools/find-orphaned-volumes #!/bin/bash # Lists PVCs not attached to a running pod kubectl get pvc --all-namespaces -o json | jq -r '.items[] | select(.status.phase=="Lost") | .metadata.name' Stop asking devs to install 14 different CLIs. We moved it all to tools/monday-cleanup

# tools/db-failover #!/bin/bash # Usage: Run when primary DB pod is stuck in CrashLoopBackoff echo "Initiating failover for database..." kubectl exec -it db-backup-pod -- ./restore-latest Keep the platform tidy without remembering complex jq queries.