Ensure shas retrieved by workflow are ordered by date #394
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The http-request-action@master is deprecated in favour of main/v1.
The response from this action does not seem to be ordered correctly (at least for the policy-controller), when curling locally the order of the tags is by date, but the action seems to be consistently returning the tags in the incorrect order:
Our nightly is therefore trying to use the policy-controller commit sha 2451921 - this commit was before the kustomization file was added and will fail due to short commit sha Kuadrant/multicluster-gateway-controller#761.
This PR sorts by the
last_modified
date and takes the last matching sha entry instead of using the default ordering taking the first matching sha entry. Once merged nightly builds should function again.