Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

fix(scripts): check every proxy read the datastore orchestration uses

Yudhi Armyndharis23ba079b5412
diff --git a/scripts/smoke-test-docker-proxy.sh b/scripts/smoke-test-docker-proxy.sh
index 3ae428cbd..68d9d84e2 100755
--- a/scripts/smoke-test-docker-proxy.sh
+++ b/scripts/smoke-test-docker-proxy.sh
@@ -48,7 +48,7 @@ echo ""
echo "==> Verifying the proxy permits the read operations orchestration needs (from openwa-api)..."
# openwa-api is the only container that can reach docker-proxy:2375 (internal network), so
# the ACL is exercised from inside it. Node's global fetch (Node 18+) avoids a curl dependency.
-for endpoint in _ping containers/json; do
+for endpoint in _ping containers/json info images/json volumes; do
CODE=$(docker exec openwa-api node -e "fetch('http://docker-proxy:2375/$endpoint').then(r=>console.log(r.status)).catch(()=>console.log(0))" 2>/dev/null || echo 0)
if [ "$CODE" != "200" ]; then
echo "FAIL: GET /$endpoint via proxy returned HTTP $CODE (expected 200)" >&2