chore: Consistent naming for VectorIO providers (#1023)

# What does this PR do?

This changes all VectorIO providers classes to follow the pattern
`<ProviderName>VectorIOConfig` and `<ProviderName>VectorIOAdapter`. All
API endpoints for VectorIOs are currently consistent with `/vector-io`.

Note that API endpoint for VectorDB stay unchanged as `/vector-dbs`. 

## Test Plan

I don't have a way to test all providers. This is a simple renaming so
things should work as expected.

---------

Signed-off-by: Yuan Tang <terrytangyuan@gmail.com>
This commit is contained in:
Yuan Tang 2025-02-13 13:15:49 -05:00 committed by GitHub
parent e4a1579e63
commit 8ff27b58fa
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
34 changed files with 85 additions and 86 deletions

View file

@ -16,7 +16,7 @@ from llama_stack.providers.utils.kvstore.config import (
@json_schema_type
class FaissImplConfig(BaseModel):
class FaissVectorIOConfig(BaseModel):
kvstore: KVStoreConfig
@classmethod