mirror of
https://github.com/Stirling-Tools/Stirling-PDF.git
synced 2026-09-02 21:03:34 +03:00
Anthony Stirling
547dce4cf3
# Description of Changes - The multi-node compose stack + behave suite (11 features) - The nightly multinode-e2e job in build-enterprise.yml cuke features are cluster_health - both nodes boot healthy and join the Valkey backplane load_balancing - traffic spreads across nodes; no spurious 401 when bounced cross_node_auth - a token from one node validates on all nodes (shared DB keys) shared_state - teams/sources/org visible from every node policy_management - create/rename/delete a policy on any node, reflected everywhere source_management - source CRUD cross-node; referenced source can't be deleted anywhere connections - S3 connection resolves (secret masked) and deletes cluster-wide processor_ledger - files processed exactly once even when both nodes trigger together policy_run_coordination - a run on one node is visible from every node rate_limiting - rate-limit counters shared via Valkey, not per node failover - LB keeps serving when a node dies; recovered node accepts existing tokens can now start a full node system with export PREMIUM_KEY=<your licence key> ./start-multinode-test.sh starts a 40 person org DB install with multi node and database (--no-seed to have without DB on startup) 4 teams 1 s3 connection 1 policy --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.
70 lines
2.7 KiB
Bash
70 lines
2.7 KiB
Bash
#!/usr/bin/env bash
|
|
# Runs the multi-node regression suite (behave features/multinode) against the clustered stack: brings it up if needed, runs non-destructive scenarios then @destructive failover ones, and restores any killed node.
|
|
# Usage: ./run-multinode-regression.sh [--no-failover] [--no-seed]
|
|
# @known_gap scenarios are expected to fail - they mark work not yet done, so a non-zero exit is fine while those are open.
|
|
set -uo pipefail
|
|
cd "$(dirname "$0")"
|
|
|
|
COMPOSE="docker compose -f docker-compose-multinode.yml"
|
|
CUKE_DIR="../cucumber"
|
|
RUN_FAILOVER=1
|
|
SEED=1
|
|
for arg in "$@"; do
|
|
case "$arg" in
|
|
--no-failover) RUN_FAILOVER=0 ;;
|
|
--no-seed) SEED=0 ;;
|
|
esac
|
|
done
|
|
|
|
echo "==> Ensuring the multi-node stack is up..."
|
|
if ! docker inspect -f '{{.State.Health.Status}}' multinode-stirling-1 2>/dev/null | grep -q healthy; then
|
|
./start-multinode-test.sh $([ "$SEED" = 0 ] && echo --no-seed) || exit 1
|
|
elif [ "$SEED" = 1 ]; then
|
|
echo " stack already up; seeding (idempotent)..."
|
|
$COMPOSE --profile seed run --rm seed >/dev/null 2>&1 || echo " (seed reported issues, continuing)"
|
|
fi
|
|
|
|
echo "==> Checking Python + behave..."
|
|
PY="${PYTHON:-python}"
|
|
command -v "$PY" >/dev/null || PY=python3
|
|
if ! "$PY" -c "import behave" 2>/dev/null; then
|
|
echo " installing test deps..."
|
|
"$PY" -m pip install -q -r "$CUKE_DIR/requirements.txt" || {
|
|
echo " could not install behave; install $CUKE_DIR/requirements.txt manually"; exit 1; }
|
|
fi
|
|
|
|
REPORT_DIR="$(pwd)/multinode/regression-report"
|
|
mkdir -p "$REPORT_DIR"
|
|
|
|
run_behave() { # $1=tags $2=label
|
|
echo "==> behave features/multinode --tags='$1' ($2)"
|
|
# behave.ini excludes features/multinode by default; -e here overrides that while still excluding the licence-gated enterprise suite.
|
|
( cd "$CUKE_DIR" && "$PY" -m behave features/multinode -e "features/enterprise" \
|
|
--tags="$1" --no-capture --format plain --format html --outfile "$REPORT_DIR/$2.html" )
|
|
return $?
|
|
}
|
|
|
|
rc=0
|
|
run_behave "~@destructive" "core" || rc=1
|
|
|
|
if [ "$RUN_FAILOVER" = 1 ]; then
|
|
run_behave "@destructive" "failover" || rc=1
|
|
echo "==> Restoring any killed nodes..."
|
|
$COMPOSE up -d >/dev/null 2>&1
|
|
for n in multinode-stirling-1 multinode-stirling-2; do
|
|
for i in $(seq 1 24); do
|
|
[ "$(docker inspect -f '{{.State.Health.Status}}' "$n" 2>/dev/null)" = "healthy" ] && break
|
|
sleep 5
|
|
done
|
|
done
|
|
fi
|
|
|
|
echo
|
|
echo "============================================================"
|
|
echo " Regression run complete. Reports: $REPORT_DIR"
|
|
echo " Exit $rc (non-zero = at least one scenario failed;"
|
|
echo " @known_gap scenarios are expected to fail - see the report)."
|
|
echo " Stack left running: http://localhost:8080 (admin / stirling)"
|
|
echo "============================================================"
|
|
exit $rc
|