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.
part of RFD 55
Description
Sorting for kube resource is weird in that it has a 1-N relationship (service to many clusters), in order to apply "sort" filter correctly, we need to extract all kube clusters from services into its own list and deduplicated.
So if a user wants to apply sort to kube clusters, they need to request
ListResources
with typeKindKubernetesCluster
that returns a list of this type. TypeKindKubernetesCluster
can only be supported through fake pagination.I contained this feature in the auth layer. It felt weird to include in the presence layer since resources returned there are
keep alive
resources (wasn't sure if this was a right thing to do though)