Repository navigation
Fix get mutating endpoints - #5191
Merged
Merged
Conversation
AWare
approved these changes
Nov 5, 2026
|
Seen on auth, image-loader, metadata-editor, thrall, cropper, collections, media-api, kahuna (merged by @lindseydew 9 minutes and 21 seconds ago) Please check your changes! |
|
Seen on leases, usage (merged by @lindseydew 11 minutes and 41 seconds ago) Please check your changes! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
This removes
/leases/reindex controllers.MediaLeaseController.reindexendpoint.This is designed to update elastic search with the latest dynamo state, and this is now fully handled in the migration step.
Modifies
/usages/digital/content/*contentId/reindex controllers.UsageApi.reindexForContent(contentId: String)from a GET to POST.
This endpoint calls CAPI and updates the
usagesstate of an image based on the response. It may be useful to run down the line, so keeping it in as a POST requestHow should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?