jcoffey-dev
c920e0f2c4
The rename commit before this one covered module paths and the obvious user-facing strings; this is the rest of it -- the places where "sentry" was a default value, a filename, or a picture rather than a word in a sentence. Defaults that changed: CLICKHOUSE_DATABASE (sentry -> cairnobs), POSTGRES_DATABASE (sentry_metadata -> cairnobs_metadata), and POSTGRES_USERNAME (sentry -> cairnobs), across api/alerting/ingest and the enterprise binaries, plus the compose files and migrate scripts that create those objects. These are *defaults*, so a deployment that sets them explicitly is unaffected -- but any deployment relying on the old defaults must have its environment updated before it picks this up, or it will come up pointing at a database that doesn't exist. Also: the light-mode logo variants (the dark ones existed alone, so the landing page and sidebar rendered a dark mark on a light background), regenerated favicons, and the docs/README/threat-model prose that still said Sentry.
34 lines
1.6 KiB
Bash
Executable File
34 lines
1.6 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Idempotently creates the topic ingest produces/consumes. Talks to
|
|
# Redpanda over the network via `rpk`, not `docker exec` into the broker
|
|
# container -- this way the same script works whether it's run from the
|
|
# host (against the standalone compose in this directory), from inside a
|
|
# sibling container on the root compose's network, or in CI.
|
|
set -euo pipefail
|
|
|
|
# NOTE: confirmed by actually running this against a live Redpanda
|
|
# container -- neither `rpk cluster health` nor `rpk topic ...` accept a
|
|
# `--brokers` flag in this rpk version. Health checks hit the Admin API
|
|
# (-X admin.hosts=..., port 9644); topic commands hit the Kafka API
|
|
# (-X brokers=..., port 9092). Getting this wrong doesn't error loudly:
|
|
# `rpk cluster health --brokers ...` fails with "unknown flag" but that
|
|
# failure was swallowed by this script's own `> /dev/null 2>&1` retry
|
|
# loop, which just silently retried the malformed command forever instead
|
|
# of ever becoming healthy.
|
|
BROKERS="${REDPANDA_BROKERS:-localhost:9092}"
|
|
ADMIN_HOSTS="${REDPANDA_ADMIN_HOSTS:-localhost:9644}"
|
|
TOPIC="${REDPANDA_TOPIC:-cairnobs.logs.raw}"
|
|
PARTITIONS="${REDPANDA_TOPIC_PARTITIONS:-6}"
|
|
|
|
echo "Waiting for Redpanda admin API at ${ADMIN_HOSTS}..."
|
|
until rpk cluster health -X "admin.hosts=${ADMIN_HOSTS}" --exit-when-healthy > /dev/null 2>&1; do
|
|
sleep 1
|
|
done
|
|
|
|
if rpk topic list -X "brokers=${BROKERS}" | awk 'NR>1{print $1}' | grep -qx "${TOPIC}"; then
|
|
echo "Topic '${TOPIC}' already exists, skipping."
|
|
else
|
|
echo "Creating topic '${TOPIC}' (${PARTITIONS} partitions)..."
|
|
rpk topic create "${TOPIC}" -X "brokers=${BROKERS}" --partitions "${PARTITIONS}" --replicas 1
|
|
fi
|