feat: implement status page endpoints #953
Merged
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.
Description
This pull request implements a backend API for the API Status Page. It includes endpoints to update and retrieve API status information, a database model to store the data, and a script to parse and post results from Newman test runs.
Related Issue (Link to issue ticket)
#952
Motivation and Context
This change is required to create a robust backend system that can efficiently process, store, and serve API health data. It solves the problem of real-time monitoring and displaying the health of various API groups, enabling automatic updates every 15 minutes on all projects and boilerplates.
How Has This Been Tested?
Unit tests were written and carried out on the GET and POST endpoints using the Pytest library
Screenshots (if appropriate - Postman, etc):
SWAGGER UI
FETCH SUCCESSFUL
POST SUCCESSFUL
RUNNING PYTHON SCRIPT TO PARSE NEWMAN JSON AND POST TO ENDPOINT
Types of changes
Checklist: