feat(backend): add demo endpoint to trigger simulated alerts#281
Merged
Conversation
Added a secure POST /demo/trigger-earthquake endpoint to main.py. It bypasses the IoT ingestion worker and publishes a crafted CRITICAL payload directly to the Redis Pub/Sub channel, enabling instant, reproducible frontend testing and live demonstrations. Closes #191
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: Pull Request
about: Standard PR format for all QuakeGuard contributions
title: "feat(backend): add demo endpoint to trigger simulated alerts"
Overview
This PR introduces a dedicated
POST /demo/trigger-earthquakeendpoint to solve the unreliability of demonstrating critical alerts during presentations and testing. Instead of waiting for the stress tester to randomly generate high-magnitude anomalies, developers can now trigger an immediate, customized CRITICAL payload directly from Swagger UI.Changes Made
src/schemas.py: Added aDemoAlertRequestPydantic model with default values (Magnitude 7.5) to allow one-click executions with an empty body.main.py: Created the/demo/trigger-earthquakeroute under thetags=["Demo"]group. Protected it withDepends(verify_api_key)and wired it directly toredis_client.publish().Impact & Next Steps
This completely decouples frontend presentation testing from the backend statistical worker layer. We can now accurately test mobile push notifications, haptic patterns, and UI state changes instantly.
Next Steps: Document this endpoint in the developer onboarding guide so team members know how to test the frontend locally without spinning up the heavy Python worker container.
Testing Performed
Related Issues
Closes #191
Closes #192
Closes #193
Closes #194
Closes #195
Closes #196