Revisiting this thread with a few months of operational experience: we’ve had to move away from the list_repositories API for performance reasons, mentioned above but apparently deepening: it’s deteriorated from slow responses to regularly and repeatedly returning 500 errors.
Our newer approach is here:
which is pretty much a continuation of this thread. It has its own drawbacks, but rather than reiterating them here I’ll let the link serve to tie the two conversations together.
@anon59622880, to your point: I am slightly miffed by the response from Sonar over there re. undocumented API usage, as our solution was what @Colin recommended above, not something we dreamed up. Recommending a way to solve our use cases and then refusing to provide any support or further recommendations when it breaks down isn’t a great developer experience, and “I wouldn’t hold my breath” isn’t a solution. 