Close
Now, even the most stressed engineer during an incident can run:
When the database is down, you don't want to Google kubectl commands.
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 ).
# tools/bootstrap-dev #!/bin/bash # Installs the exact versions of Terragrunt, Helm, and Node used in production ./tools/install-tfenv && tfenv install ./tools/install-helm-3.14 A tools/ folder is useless if nobody knows how to invoke it. Add a Makefile at your repo root to act as the catalog.
# 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.
Now, even the most stressed engineer during an incident can run:
When the database is down, you don't want to Google kubectl commands. 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 ). Now, even the most stressed engineer during an
# tools/bootstrap-dev #!/bin/bash # Installs the exact versions of Terragrunt, Helm, and Node used in production ./tools/install-tfenv && tfenv install ./tools/install-helm-3.14 A tools/ folder is useless if nobody knows how to invoke it. Add a Makefile at your repo root to act as the catalog. And nothing reduces toil like a folder full
# 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.
