Implement complete database schema and Flask application structure for SneakyScan web interface. This establishes the foundation for web-based scan management, scheduling, and visualization. Database & ORM: - Add 11 SQLAlchemy models for comprehensive scan data storage (Scan, ScanSite, ScanIP, ScanPort, ScanService, ScanCertificate, ScanTLSVersion, Schedule, Alert, AlertRule, Setting) - Configure Alembic migrations system with initial schema migration - Add init_db.py script for database initialization and password setup - Support both migration-based and direct table creation Settings System: - Implement SettingsManager with automatic encryption for sensitive values - Add Fernet encryption for SMTP passwords and API tokens - Implement PasswordManager with bcrypt password hashing (work factor 12) - Initialize default settings for SMTP, authentication, and retention Flask Application: - Create Flask app factory pattern with scoped session management - Add 4 API blueprints: scans, schedules, alerts, settings - Implement functional Settings API (GET/PUT/DELETE endpoints) - Add CORS support, error handlers, and request/response logging - Configure development and production logging to file and console Docker & Deployment: - Update Dockerfile to install Flask dependencies - Add docker-compose-web.yml for web application deployment - Configure volume mounts for database, output, and logs persistence - Expose port 5000 for Flask web server Testing & Validation: - Add validate_phase1.py script to verify all deliverables - Validate directory structure, Python syntax, models, and endpoints - All validation checks passing Documentation: - Add PHASE1_COMPLETE.md with comprehensive Phase 1 summary - Update ROADMAP.md with Phase 1 completion status - Update .gitignore to exclude database files and documentation Files changed: 21 files - New: web/ directory with complete Flask app structure - New: migrations/ with Alembic configuration - New: requirements-web.txt with Flask dependencies - Modified: Dockerfile, ROADMAP.md, .gitignore
151 lines
3.5 KiB
Python
151 lines
3.5 KiB
Python
"""
|
|
Schedules API blueprint.
|
|
|
|
Handles endpoints for managing scheduled scans including CRUD operations
|
|
and manual triggering.
|
|
"""
|
|
|
|
from flask import Blueprint, jsonify, request
|
|
|
|
bp = Blueprint('schedules', __name__)
|
|
|
|
|
|
@bp.route('', methods=['GET'])
|
|
def list_schedules():
|
|
"""
|
|
List all schedules.
|
|
|
|
Returns:
|
|
JSON response with schedules list
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
return jsonify({
|
|
'schedules': [],
|
|
'message': 'Schedules list endpoint - to be implemented in Phase 3'
|
|
})
|
|
|
|
|
|
@bp.route('/<int:schedule_id>', methods=['GET'])
|
|
def get_schedule(schedule_id):
|
|
"""
|
|
Get details for a specific schedule.
|
|
|
|
Args:
|
|
schedule_id: Schedule ID
|
|
|
|
Returns:
|
|
JSON response with schedule details
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
return jsonify({
|
|
'schedule_id': schedule_id,
|
|
'message': 'Schedule detail endpoint - to be implemented in Phase 3'
|
|
})
|
|
|
|
|
|
@bp.route('', methods=['POST'])
|
|
def create_schedule():
|
|
"""
|
|
Create a new schedule.
|
|
|
|
Request body:
|
|
name: Schedule name
|
|
config_file: Path to YAML config
|
|
cron_expression: Cron-like schedule expression
|
|
|
|
Returns:
|
|
JSON response with created schedule ID
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
data = request.get_json() or {}
|
|
|
|
return jsonify({
|
|
'schedule_id': None,
|
|
'status': 'not_implemented',
|
|
'message': 'Schedule creation endpoint - to be implemented in Phase 3',
|
|
'data': data
|
|
}), 501
|
|
|
|
|
|
@bp.route('/<int:schedule_id>', methods=['PUT'])
|
|
def update_schedule(schedule_id):
|
|
"""
|
|
Update an existing schedule.
|
|
|
|
Args:
|
|
schedule_id: Schedule ID to update
|
|
|
|
Request body:
|
|
name: Schedule name (optional)
|
|
config_file: Path to YAML config (optional)
|
|
cron_expression: Cron-like schedule expression (optional)
|
|
enabled: Whether schedule is active (optional)
|
|
|
|
Returns:
|
|
JSON response with update status
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
data = request.get_json() or {}
|
|
|
|
return jsonify({
|
|
'schedule_id': schedule_id,
|
|
'status': 'not_implemented',
|
|
'message': 'Schedule update endpoint - to be implemented in Phase 3',
|
|
'data': data
|
|
}), 501
|
|
|
|
|
|
@bp.route('/<int:schedule_id>', methods=['DELETE'])
|
|
def delete_schedule(schedule_id):
|
|
"""
|
|
Delete a schedule.
|
|
|
|
Args:
|
|
schedule_id: Schedule ID to delete
|
|
|
|
Returns:
|
|
JSON response with deletion status
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
return jsonify({
|
|
'schedule_id': schedule_id,
|
|
'status': 'not_implemented',
|
|
'message': 'Schedule deletion endpoint - to be implemented in Phase 3'
|
|
}), 501
|
|
|
|
|
|
@bp.route('/<int:schedule_id>/trigger', methods=['POST'])
|
|
def trigger_schedule(schedule_id):
|
|
"""
|
|
Manually trigger a scheduled scan.
|
|
|
|
Args:
|
|
schedule_id: Schedule ID to trigger
|
|
|
|
Returns:
|
|
JSON response with triggered scan ID
|
|
"""
|
|
# TODO: Implement in Phase 3
|
|
return jsonify({
|
|
'schedule_id': schedule_id,
|
|
'scan_id': None,
|
|
'status': 'not_implemented',
|
|
'message': 'Manual schedule trigger endpoint - to be implemented in Phase 3'
|
|
}), 501
|
|
|
|
|
|
# Health check endpoint
|
|
@bp.route('/health', methods=['GET'])
|
|
def health_check():
|
|
"""
|
|
Health check endpoint for monitoring.
|
|
|
|
Returns:
|
|
JSON response with API health status
|
|
"""
|
|
return jsonify({
|
|
'status': 'healthy',
|
|
'api': 'schedules',
|
|
'version': '1.0.0-phase1'
|
|
})
|