Correct use of gcloud –sort-by combined with –limit
I’m using Google Cloud KMS, and I try to get the latest version of a specific asymmetric key with gcloud cli
(v492.0). It seems that the --limit
flag doesn’t take into account the sorting direction provided by --sort-by
. Sorting is getting applied after the limit, in my opinion this is wrong and sorting should happen first then the limit.