Skip to content

Revert a 14.0 change in the deployments API

What does this MR do?

Brings back the updated_after/updated_before parameter of the deployments API.

This was changed in !63541 (diffs), but seems I confused updated_at with updated_after.

updated_at is in the API response, it's not a parameter 🤦🏼

So, to sum up:

  • updated_at was not dropped from the response in 14.0
  • updated_after/updated_before is not yet implemented as a paremeter

Related issues

Author's checklist

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Achilleas Pipinellis

Merge request reports