mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-10-23 00:27:26 +00:00
**This PR changes configurations in a backward incompatible way.** Run configs today repeat full SQLite/Postgres snippets everywhere a store is needed, which means duplicated credentials, extra connection pools, and lots of drift between files. This PR introduces named storage backends so the stack and providers can share a single catalog and reference those backends by name. ## Key Changes - Add `storage.backends` to `StackRunConfig`, register each KV/SQL backend once at startup, and validate that references point to the right family. - Move server stores under `storage.stores` with lightweight references (backend + namespace/table) instead of full configs. - Update every provider/config/doc to use the new reference style; docs/codegen now surface the simplified YAML. ## Migration Before: ```yaml metadata_store: type: sqlite db_path: ~/.llama/distributions/foo/registry.db inference_store: type: postgres host: ${env.POSTGRES_HOST} port: ${env.POSTGRES_PORT} db: ${env.POSTGRES_DB} user: ${env.POSTGRES_USER} password: ${env.POSTGRES_PASSWORD} conversations_store: type: postgres host: ${env.POSTGRES_HOST} port: ${env.POSTGRES_PORT} db: ${env.POSTGRES_DB} user: ${env.POSTGRES_USER} password: ${env.POSTGRES_PASSWORD} ``` After: ```yaml storage: backends: kv_default: type: kv_sqlite db_path: ~/.llama/distributions/foo/kvstore.db sql_default: type: sql_postgres host: ${env.POSTGRES_HOST} port: ${env.POSTGRES_PORT} db: ${env.POSTGRES_DB} user: ${env.POSTGRES_USER} password: ${env.POSTGRES_PASSWORD} stores: metadata: backend: kv_default namespace: registry inference: backend: sql_default table_name: inference_store max_write_queue_size: 10000 num_writers: 4 conversations: backend: sql_default table_name: openai_conversations ``` Provider configs follow the same pattern—for example, a Chroma vector adapter switches from: ```yaml providers: vector_io: - provider_id: chromadb provider_type: remote::chromadb config: url: ${env.CHROMADB_URL} kvstore: type: sqlite db_path: ~/.llama/distributions/foo/chroma.db ``` to: ```yaml providers: vector_io: - provider_id: chromadb provider_type: remote::chromadb config: url: ${env.CHROMADB_URL} persistence: backend: kv_default namespace: vector_io::chroma_remote ``` Once the backends are declared, everything else just points at them, so rotating credentials or swapping to Postgres happens in one place and the stack reuses a single connection pool. |
||
---|---|---|
.. | ||
changelog.yml | ||
conformance.yml | ||
install-script-ci.yml | ||
integration-auth-tests.yml | ||
integration-sql-store-tests.yml | ||
integration-tests.yml | ||
integration-vector-io-tests.yml | ||
pre-commit.yml | ||
precommit-trigger.yml | ||
providers-build.yml | ||
providers-list-deps.yml | ||
python-build-test.yml | ||
README.md | ||
record-integration-tests.yml | ||
semantic-pr.yml | ||
stale_bot.yml | ||
test-external-provider-module.yml | ||
test-external.yml | ||
ui-unit-tests.yml | ||
unit-tests.yml |
Llama Stack CI
Llama Stack uses GitHub Actions for Continuous Integration (CI). Below is a table detailing what CI the project includes and the purpose.
Name | File | Purpose |
---|---|---|
Update Changelog | changelog.yml | Creates PR for updating the CHANGELOG.md |
API Conformance Tests | conformance.yml | Run the API Conformance test suite on the changes. |
Installer CI | install-script-ci.yml | Test the installation script |
Integration Auth Tests | integration-auth-tests.yml | Run the integration test suite with Kubernetes authentication |
SqlStore Integration Tests | integration-sql-store-tests.yml | Run the integration test suite with SqlStore |
Integration Tests (Replay) | integration-tests.yml | Run the integration test suites from tests/integration in replay mode |
Vector IO Integration Tests | integration-vector-io-tests.yml | Run the integration test suite with various VectorIO providers |
Pre-commit | pre-commit.yml | Run pre-commit checks |
Pre-commit Bot | precommit-trigger.yml | Pre-commit bot for PR |
Test Llama Stack Build | providers-build.yml | Test llama stack build |
Test llama stack list-deps | providers-list-deps.yml | Test llama stack list-deps |
Python Package Build Test | python-build-test.yml | Test building the llama-stack PyPI project |
Integration Tests (Record) | record-integration-tests.yml | Run the integration test suite from tests/integration |
Check semantic PR titles | semantic-pr.yml | Ensure that PR titles follow the conventional commit spec |
Close stale issues and PRs | stale_bot.yml | Run the Stale Bot action |
Test External Providers Installed via Module | test-external-provider-module.yml | Test External Provider installation via Python module |
Test External API and Providers | test-external.yml | Test the External API and Provider mechanisms |
UI Tests | ui-unit-tests.yml | Run the UI test suite |
Unit Tests | unit-tests.yml | Run the unit test suite |