Description of changes

Adds a method to the admin client to list all databases for a tenant. Has limit/offset parameters similar to how listing collections works.

The implementation for distributed Chroma is in a separate PR, next in this stack: https://github.com/chroma-core/chroma/pull/3440.

See https://github.com/chroma-core/hosted-chroma/issues/900 for main tracking issue.

Test plan

How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

Updated.

Jan 08 '25 00:01 codetheweb

Please leverage this checklist to ensure your code review is thorough before approving

[ ] Can you think of any use case in which the code does not behave as intended? Have they been tested?
[ ] Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
[ ] If appropriate, are there adequate property based tests?
[ ] If appropriate, are there adequate unit tests?
[ ] Should any logging, debugging, tracing information be added or removed?
[ ] Are error messages user-friendly?
[ ] Have all documentation changes needed been made?
[ ] Have all non-obvious changes been commented?

[ ] Are there any potential impacts on other parts of the system or backward compatibility?
[ ] Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

[ ] Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Jan 08 '25 00:01 github-actions[bot]

This stack of pull requests is managed by Graphite. Learn more about stacking.

Jan 09 '25 00:01 codetheweb

Jan 9, 7:38 PM EST: A user started a stack merge that includes this pull request via Graphite.
Jan 9, 7:39 PM EST: A user merged this pull request with Graphite.

Jan 10 '25 00:01 codetheweb