feat: Allow deleting all timestamps when lastReceived is omitted from delete alert API #3787
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.
Closes #2817
📑 Description
Currently, the DELETE /alerts API allows only a specific timestamp to be deleted or restored at a time, requiring lastReceived to be provided.
This update enhances the API by allowing all timestamps associated with an alert's fingerprint to be deleted when lastReceived is omitted.
✅ Checks
ℹ Additional Information