-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change imagestreamtag sorting #17430
Change imagestreamtag sorting #17430
Conversation
/test |
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
3708d5b
to
5ba167d
Compare
a6d7721
to
74aa730
Compare
The error from test is valid:
Latest has to go first always. |
Signed-off-by: Michal Minář <[email protected]>
Make sure that 'v' prefix is taken into account. Sort identical tag names with 'v' prefix at the end. Signed-off-by: Michal Minář <[email protected]>
74aa730
to
691009b
Compare
@soltysh this list is a result of conversion from internal to v1 scheme, right? Why the The |
not having :latest in the list of imported tags (when the # of tags we import is limited) will likely cause problems :-) I would pickup :latest as first and then every other tags. |
That conversion also does sorting, iirc. I had a discussion with @smarterclayton about it long time ago. We need to provide stable output, both from our CLI and API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, miminar, soltysh The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
As I said before, the change doesn't affect which tags the importer picks up. It affects the order of tags in a serialized image stream though. I don't see it as very important but you may know better. @smarterclayton suggested to start sorting the tags in conversions alphabetically to have a stable sort algorithm without bugs :-). |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 16538, 17430, 17432, 17433, 17442). |
@miminar: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Automatic merge from submit-queue (batch tested with PRs 17451, 17501). Fix tag prioritization "v" tag prefix has the least priority. A follow-up for #17430
/cherry-pick release-3.7 |
Forward-port of openshift/ose#932