You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,6 +245,35 @@ CacheBolt exposes Prometheus-compatible metrics at the `/metrics` endpoint on po
245
245
-`cachebolt_fallback_miss_total`
246
246
Count of failover attempts that missed both memory and persistent storage.
247
247
248
+
---
249
+
## 🧹 Cache Invalidation
250
+
251
+
You can clear the entire cache (both in-memory and persistent storage) using the `/cache?backend=true` endpoint. This is useful when deploying major updates or invalidating stale content globally.
252
+
253
+
- When `backend=true`, CacheBolt will delete all cache entries stored in:
254
+
- 🟢 Amazon S3
255
+
- 🔵 Google Cloud Storage
256
+
- 🔶 Azure Blob Storage
257
+
- 💽 Local Filesystem
258
+
259
+
### ❌ Pattern-based deletion limitations
260
+
261
+
If you attempt to use `pattern=...` with `backend=true`, CacheBolt will return an error. Pattern-based invalidation is **only supported in-memory**, not in persistent storage.
0 commit comments