aws / aws/containers-roadmap

[EKS] [request]: Return list-updates in reversed chronological order

Open
#1,439 1 comment 0 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
When requesting a list-updates the updates are returned in random order. The only way to figure out what the latest update is, is to do a list-update and then a describe-update of every update found and comparing all submission times. This becomes more cumbersome the longer the update history is.

Please return the updates in reversed chronological order

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Figure out if the latest update failed.

**Are you currently working around this issue?**
list -> loop -> compare.

Contributor guide

Open the contributing guide

Research direction

Review the EKS list-updates and describe-update operations, focusing on how update submission times are exposed and ordered. Done means list-updates returns updates in reversed chronological order so the latest update can be identified without describing every result.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.