[TASK] Implement delete pushed assets endpoint
Open
Beginner friendly
Nobody has claimed this yet.
stale
Team : Modernization
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Implement DELETE /v1/maintenance/_pushedAssets in MaintenanceResource.java. Deletes all records from the pushed assets tracking table, clearing the entire push publishing history.
Acceptance Criteria
- Endpoint must call
APILocator.getPushedAssetsAPI().deleteAllPushedAssets() - API caller must receive a success message on completion
- API caller must receive an error message if deletion fails
- Must require CMS Administrator role and Maintenance portlet access
Priority
None
Additional Context
- This clears the push publishing history — all assets will appear as "never pushed" to all endpoints
- Used when resetting push publishing state or troubleshooting push issues
- DWR legacy:
CMSMaintenanceAjax.deletePushedAssets()lines 244–258
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 MaintenanceResource.java and compare the DWR legacy implementation in CMSMaintenanceAjax.deletePushedAssets(), lines 244–258. Implement the DELETE endpoint using the specified pushed-assets API, enforcing the CMS Administrator role and Maintenance portlet access; done means successful and failure messages are returned as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100