Expose a cache-purge endpoint for the edge #29

New issue

Closed

opened 2026-07-01 00:58:21 +00:00 by manlycucumber · 1 comment

manlycucumber commented

2026-07-01 00:58:21 +00:00

(Migrated from github.com)

Problem

The admin rebuild flow and ad-hoc operations need a reliable way to purge Cloudflare. A dedicated, authenticated purge mechanism isolates that concern.

Acceptance criteria

An authenticated endpoint/command purges the edge cache by key prefix or globally.
Purge requests are rejected without admin credentials.
Purge results are returned with per-target status.
The purge path is covered by tests against a stubbed edge API.

Notes

Keep purge credentials out of the repo; load from environment/secret store.

## Problem The admin rebuild flow and ad-hoc operations need a reliable way to purge Cloudflare. A dedicated, authenticated purge mechanism isolates that concern. ## Acceptance criteria - [ ] An authenticated endpoint/command purges the edge cache by key prefix or globally. - [ ] Purge requests are rejected without admin credentials. - [ ] Purge results are returned with per-target status. - [ ] The purge path is covered by tests against a stubbed edge API. ## Notes Keep purge credentials out of the repo; load from environment/secret store.

manlycucumber commented

2026-07-03 06:19:01 +00:00

(Migrated from github.com)

Delivered in #138 (squash-merged to develop).

Delivered in #138 (squash-merged to `develop`).

manlycucumber referenced this issue from a commit

2026-08-05 19:02:25 +00:00

feat: admin rebuild/purge and the AUP + terms endpoints (#138)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#29

No description provided.

Rows
Columns