-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathTODO
More file actions
49 lines (47 loc) · 3.15 KB
/
TODO
File metadata and controls
49 lines (47 loc) · 3.15 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
@28/06/2025 - Add `check_type` field to `Website` model:
Todo:
✔ Add `check_type` field to `Website` model @done(25-06-28 15:53)
Define `check_type` as an Enum with values `HTTP`, `PING` ?DNS
Find out viability of DNS
Ensure `check_type` is optional with a default value of `HTTP`
✔ Add database migration to include `check_type` field @done(25-06-28 16:37)
Define enum in migration file manually as alembic does not automatically create enum type in the database before trying to use it in a column.
Why is this important? Postgresql treats enums as a database type that must exist before they can be used in a column definition.
Create migration script to add `check_type` field to the `Website` table with alembic
Run migration to update the database schema
✔ Add `check_type` field to schemas @done(25-06-28 16:43)
✔ Update `WebsiteBase` schema to include `check_type` @done(25-06-28 16:43)
WebsiteCreate and WebsiteRead inherit from `WebsiteBase`
✔ Update `WebsiteUpdate` schema to include `check_type` @done(25-06-28 16:43)
✘ Update API endpoints to include `check_type` @cancelled(25-06-28 16:45)
✘ Update `create_website` endpoint to accept `check_type` @cancelled(25-06-28 16:45)
✘ Update `update_website` endpoint to accept `check_type` @cancelled(25-06-28 16:45)
✔ Update `check_website_uptime` task to handle `check_type` @done(25-07-16 10:14)
✔ Modify the task to perform different checks based on `check_type` @done(25-07-16 10:14)
✔ Ensure that the task can handle both HTTP and PING checks @done(25-07-16 10:14)
☐ Update tests to include `check_type`
☐ Modify `create_website` endpoint tests to include `check_type`
☐ Modify `update_website` endpoint tests to include `check_type`
☐ Modify `get_websites` endpoint tests to include `check_type`
☐ Modify `check_website_uptime` task tests to handle different `check_type` values
@15/06/2025 - Add `AdHocSSLLog` model:
Todo:
To allow logging of ssl checks for adhoc sites
✔ Create `AdHocSSLLog` model @done(25-07-17 11:04)
✔ Create and apply migration @done(25-07-17 11:04)
✔ Define `APIKey` model @done(25-07-17 11:06)
✔ Create and apply migration @done(25-07-17 11:06)
? api_key_id in AdHocSSLLog is nullable, should we consider giving a limited number of checks if unauthenticated @important
✔ Update `check_ssl_status_task` @done(25-07-17 11:44)
Update the task to log to AdHocSSLLog for ad hoc checks (website_id=None) and SSLLog for stored websites, including api_key_id for ad hoc logs
✔ Update the `/ssl-checks` Endpoint @done(25-07-17 12:23)
Update the endpoint to require API key authentication and pass api_key_id to the task.
✔ Add dependency to validate `api_key` @done(25-07-17 12:22)
✔ Pass dependency to endpoint, then pass to invocation of `check_ssl_status_task` @done(25-07-17 12:23)
@18/07/25 - API Key generation and rate limiting on /ssl-checks:
Todo:
Handle API key generation and rate limit the public /ssl-checks endpoint
✔ Create endpoint to trigger api key generation @done(25-07-18 10:47)
✔ Add `APIKeyResponse` schema @done(25-07-18 10:47)
☐ Implement rate limiting
☐