// the find
HariSekhon/DevOps-Bash-tools
1000+ DevOps Bash Scripts - AWS, GCP, Kubernetes, Docker, CI/CD, APIs, SQL, PostgreSQL, MySQL, Hive, Impala, Kafka, Hadoop, Jenkins, GitHub, GitLab, BitBucket, Azure DevOps, TeamCity, Spotify, MP3, LDAP, Code/Build Linting, pkg mgmt for Linux, Mac, Python, Perl, Ruby, NodeJS, Golang, Advanced dotfiles: .bashrc, .vimrc, .gitconfig, .screenrc, tmux..
A personal collection of 1000+ shell scripts and dotfiles built up over years of DevOps work, covering everything from AWS/GCP/Kubernetes automation to Spotify playlist management. This is one person's battle-tested toolkit, not a framework — you're meant to clone it and source it into your shell. Best suited for platform engineers who want a head start on boilerplate CLI automation rather than people looking for installable tools.
The breadth of coverage is genuinely useful: the AWS IAM scripts alone (access key age reports, MFA checks, CIS hardening) would take days to write from scratch. The `.bash.d/` library is well-organized with per-technology files instead of one giant `.bashrc`, which makes it actually maintainable. ShellCheck CI on every push means the scripts don't have the obvious quoting and word-splitting bugs that plague most ad-hoc shell collections. The git-secrets hook templates included in `.git-templates/` are a practical addition that many teams miss.
The repo is fundamentally a personal dotfiles repo that has grown to 1000+ files — there's no real discoverability mechanism beyond grep and the README index, and the README itself is so long it's hard to find anything. Scripts have implicit dependencies (jq, aws-cli, specific Python versions) that are documented nowhere per-script; the bootstrap script installs everything or nothing. No versioning or stability guarantees: a script that works today may change tomorrow since it's a living personal toolkit with no changelog. The Hadoop/Cloudera/Impala coverage is dated and likely unmaintained — those sections haven't been relevant for most shops in years.