Add "updated_after" parameter to the Deployments API endpoint
Summary
An Enterprise customer is pulling data from the "list project deployments" API endpoint to populate a custom-built dashboard. The customer only wants to display the latest changes. However, the customer has no way to restrict the API results to the latest changes. Instead, the customer retrieves all records, checks one-by-one and processes only the records updated after the latest updated_at value in the last batch retrieved. The customer has asked for the ability to query for updated_at values after a specified timestamp.
The API currently offers an updated_after parameter for multiple resource "list" endpoints, including Issues and Merge Requests. The same functionality can be replicated for Deployments.
Spec
The "list project deployments" API endpoint accepts an updated_after parameter.
Spec Notes
- It makes sense to add
updated_beforeat the same time, as that is effectively part of the same feature, if it's not much work. - The groundwork has been laid by !17913 (merged), which adds timestamps to the Deployments API response.
- There is a similar issue to Add "updated_after" parameter to the Pipelines API endpoint