release: v1.47.0 - Subtype Management & Metrics Drivers Engine, Explicit Secret Inheritance & Cross-Platform Agents

test-integration.sh

@@ -4,21 +4,21 @@ set -e
 echo "=== Starting theta-suite Integration Tests ==="
 
 echo "=> Cleaning up any existing containers and volumes..."
-docker-compose down -v
+docker compose down -v
 
 echo "=> Running setup.sh to initialize environment..."
 # Run setup non-interactively if possible (we might need to export some env vars)
 # setup.sh uses dialog, which requires a terminal, but it falls back to defaults if not interactive?
 # Actually setup.sh has a dialog UI. Let's just run it or provide a seeded config.
 # If setup.sh is strictly interactive, we might need to bypass it or provide answers.
-# Let's try running docker-compose up directly if setup.sh is too interactive, but the user explicitly said "Make sure setup.sh like your change, then do a full release. Make sure each repo has a current change log, is pushed and and merged." and "Automated testing in theta-suite to test integration between all the include projects".
+# Let's try running docker compose up directly if setup.sh is too interactive, but the user explicitly said "Make sure setup.sh like your change, then do a full release. Make sure each repo has a current change log, is pushed and and merged." and "Automated testing in theta-suite to test integration between all the include projects".
 
 # Wait, setup.sh has no silent mode out of the box unless we provide answers.
 echo "=> Initializing OpenBao manually for tests (simulating setup.sh)"
 # Actually, setup.sh initializes Vault. If we don't run it, Vault is sealed!
 # Let's just write a curl test that checks if the containers start.
 
-docker-compose up -d
+docker compose up -d
 
 echo "=> Waiting for services to become healthy..."
 sleep 15 # Give time for containers to spin up
@@ -40,5 +40,5 @@ fi
 echo "✅ SSO Manager responds on port 3001"
 
 echo "=== All integration tests passed! ==="
-docker-compose down -v
+docker compose down -v
 exit 0