- Add discovery_results table to database schema
- Create persistent discovery service with database storage
- Update dashboard API to use persistent discovery service
- Initialize persistent discovery service on application startup
- Fix 404 errors when polling discovery scan results
Fixed TypeError in SSHDeployer.execute_remote() method by adding 'silent' parameter
- Added silent parameter with default value False
- Modified print statements to respect silent mode
- Health checks now work correctly during deployment
This ensures the deployment script can properly wait for services to start and validate the deployment
Updated references in:
- deploy/deploy-onprem.sh: Fixed paths for test-deployment.sh and test_dashboard_local.py
- deploy/validate-deployment.sh: Fixed path for test-e2e-deployment.py
- tests/integration/test-e2e-deployment.py: Fixed paths for mock servers
All file references now point to correct locations in the new organized structure
- Add discovery protocol test files for debugging and direct testing
- Add remote test integration scripts and configuration
- Update deployment and monitoring scripts with recent changes
- Include test-remote.yml configuration for remote testing
- Created test.yml configuration file for test environment
- Created .env.test environment file with protocol servers enabled
- Updated deployment script to handle test environment
- Test environment uses port 8081 and enables protocol servers for testing
- Created .env.production with OPCUA_ENABLED=false and MODBUS_ENABLED=false
- Created docker-compose.production.yml that uses production environment file
- Updated deployment script to use production docker-compose file when available
- This prevents connection issues when protocol servers are not available
openhands