Add "updated_after" parameter to the Pipelines API endpoint
Summary
An Enterprise customer is pulling data from the "list project pipelines" 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 Pipelines.
Spec
The "list project pipelines" API endpoint accepts an updated_after
parameter.
Spec Notes
- It makes sense to add
updated_before
at the same time, if it's not much work. - The groundwork has been laid by !17911 (merged), which adds timestamps to the Pipelines API response.
- There is a similar issue to Add "updated_after" parameter to the Deployments API endpoint