[TASK] Fix flush-all endpoint missing side effects
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Modify the existing DELETE /v1/caches/provider/{provider}/flush endpoint in CacheResource.java to add missing side effects. Currently it only calls MaintenanceUtil.flushCache() but the JSP Struts action also resets permission references and reloads PushPublishing filters after flushing all caches.
Acceptance Criteria
- After calling
MaintenanceUtil.flushCache(), endpoint must also callAPILocator.getPermissionAPI().resetAllPermissionReferences() - After calling
MaintenanceUtil.flushCache(), endpoint must also callDotInitializer.class.cast(APILocator.getPublisherAPI()).init()to reload PushPublishing filters - Existing behavior (flushing all caches) must not change
- Existing response format must not change
Priority
None
Additional Context
- Current implementation:
CacheResource.javaline 338,flushAll()method - Only consumer is a Postman test collection — no breaking change risk
- The Struts action (
ViewCMSMaintenanceAction._flush()) always callsresetAllPermissionReferences()and conditionally reloads PushPublishing filters — the REST endpoint was missing both
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 in CacheResource.java at line 338, in the flushAll() method, and compare its behavior with ViewCMSMaintenanceAction._flush(). Verify the existing Postman test collection for the DELETE /v1/caches/provider/{provider}/flush endpoint, then confirm the permission references and PushPublishing filters are reloaded after cache flushing without changing the response format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100