Objectstore allow clearing entries on 404
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: files
feature: filesystem
feature: object storage
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
If for some reason the filecache has a file in there that is no longer on the objectstore we get back a 404 when we try to access that file.
since there is no way to scan the object store currently. It would be great to have the admin to set a flag to kill them.
CC: @icewind1991
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the filecache path that accesses the objectstore and handles a 404, then inspect how admin settings are defined and applied. The issue does not name files or tests, so first locate those entry points. Done means an administrator can enable the requested behavior and stale entries are handled when the objectstore returns 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100