This issue is secondary to KEYCLOAK-14523 which I recently reported. During a name-based operation, e.g.
the admin CLI uses the REST API to request all resources of that type (in this case groups) and does a search for the group by name to find the id associated with that resource which is then used in a subsequent REST request. This can be made much more efficient by implementing all of that logic on the server side and also by adding REST endpoints that allow resources to be addressed by other unique properties. For example, groups could be addressed by name or path which would then require a single round-trip with a more efficient SQL query on the server side to implement operations on the group.