Skip to content

Instantly share code, notes, and snippets.

@tsibley

tsibley/heroku-redis-cli

Created September 19, 2024 21:07
Show Gist options
  • Save tsibley/6f82bcaadf25869b0251f68d8be8d9b5 to your computer and use it in GitHub Desktop.
Save tsibley/6f82bcaadf25869b0251f68d8be8d9b5 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
heroku-redis-cli
#!/bin/bash
set -euo pipefail
app_db="${1:?usage: $(basename "$0") <app-name>[/<database-name>]}"
shift
app="${app_db%%/*}"
db="${app_db#*/}"
url="$(heroku redis:credentials -a "$app" "$db")"
pass="$(<<<"$url" grep -m1 -oP '[^:]+(?=@)')"
host="$(<<<"$url" cut -d@ -f2 | cut -d: -f1)"
port="$(<<<"$url" cut -d@ -f2 | cut -d: -f2)"
# Heroku Redis' TLS socket is documented to be on the next port up from the non-TLS port.
if [[ "$url" == redis:* ]]; then
port=$((port+1))
fi
export REDISCLI_AUTH="$pass"
# Heroku's Redis uses self-signed certs instead of specific CA (even a self-CA)
# we can trust. Ugh. This means active snooping is still possible with MITM,
# but at least passing snooping is blocked.
exec redis.cli --tls -h "$host" -p "$port" --insecure "$@"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment