feat: add tiered cache invalidation#378
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e579e80dee
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| if len(caches) == 1 { | ||
| return caches[0] | ||
| } | ||
| return Tiered{caches} |
There was a problem hiding this comment.
Preserve unsupported stats for single-tier caches
When exactly one backend is configured, wrapping it in Tiered changes unsupported operations into successful empty results: Tiered.Stats skips ErrStatsUnavailable and then returns a zero Stats, and ListNamespaces similarly returns an empty slice. For a lone S3 or noop cache this makes /api/v1/stats report 200 with fabricated zero capacity/object counts instead of the backend's unsupported error, which can mislead monitoring and clients; the previous single-cache passthrough avoided this.
Useful? React with 👍 / 👎.
No description provided.