phoenix-oss/llama-stack-mirror
0
0
Fork 1
mirror of https://github.com/meta-llama/llama-stack.git synced 2025-07-27 14:38:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: separate build and run provider types (#2917)
Some checks failed
Coverage Badge / unit-tests (push) Failing after 1s
Details
Integration Auth Tests / test-matrix (oauth2_token) (push) Failing after 1s
Details
Integration Tests / discover-tests (push) Successful in 3s
Details
SqlStore Integration Tests / test-postgres (3.13) (push) Failing after 4s
Details
Vector IO Integration Tests / test-matrix (3.12, inline::faiss) (push) Failing after 4s
Details
Vector IO Integration Tests / test-matrix (3.12, inline::milvus) (push) Failing after 5s
Details
Vector IO Integration Tests / test-matrix (3.12, inline::sqlite-vec) (push) Failing after 5s
Details
Vector IO Integration Tests / test-matrix (3.12, remote::pgvector) (push) Failing after 4s
Details
Vector IO Integration Tests / test-matrix (3.13, inline::faiss) (push) Failing after 5s
Details
Test Llama Stack Build / generate-matrix (push) Successful in 4s
Details
Vector IO Integration Tests / test-matrix (3.13, inline::milvus) (push) Failing after 5s
Details
Python Package Build Test / build (3.13) (push) Failing after 2s
Details
Test Llama Stack Build / build-single-provider (push) Failing after 3s
Details
Python Package Build Test / build (3.12) (push) Failing after 2s
Details
Vector IO Integration Tests / test-matrix (3.13, inline::sqlite-vec) (push) Failing after 5s
Details
Vector IO Integration Tests / test-matrix (3.12, remote::chromadb) (push) Failing after 6s
Details
Test Llama Stack Build / build-ubi9-container-distribution (push) Failing after 3s
Details
Vector IO Integration Tests / test-matrix (3.13, remote::chromadb) (push) Failing after 5s
Details
Test Llama Stack Build / build-custom-container-distribution (push) Failing after 4s
Details
Vector IO Integration Tests / test-matrix (3.13, remote::pgvector) (push) Failing after 5s
Details
SqlStore Integration Tests / test-postgres (3.12) (push) Failing after 9s
Details
Test External Providers Installed via Module / test-external-providers-from-module (venv) (push) Failing after 6s
Details
Test External API and Providers / test-external (venv) (push) Failing after 5s
Details
Update ReadTheDocs / update-readthedocs (push) Failing after 4s
Details
Unit Tests / unit-tests (3.13) (push) Failing after 5s
Details
Test Llama Stack Build / build (push) Failing after 3s
Details
Unit Tests / unit-tests (3.12) (push) Failing after 5s
Details
Integration Tests / test-matrix (push) Failing after 7s
Details
Pre-commit / pre-commit (push) Successful in 1m13s
Details

Browse source 
# What does this PR do?

in #2637, I combined the run and build config provider types to both use
`Provider`

since this includes a provider_id, a user must now specify this when
writing a build yaml. This is not very clear because all a user should
care about upon build is the code to be installed (the module and the
provider_type)

introduce `BuildProvider` and fixup the parts of the code impacted by
this

Signed-off-by: Charlie Doern <cdoern@redhat.com>
This commit is contained in:
Charlie Doern 2025-07-25 15:39:26 -04:00 • committed by GitHub
parent 025163d8e6
commit 3344d8a9e5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
19 changed files with 401 additions and 754 deletions
Download patch file Download diff file Expand all files Collapse all files

3
llama_stack/distribution/configure.py
View file

@ -100,11 +100,12 @@ def configure_api_providers(config: StackRunConfig, build_spec: DistributionSpec
break
logger.info(f"> Configuring provider `({provider.provider_type})`")
pid = provider.provider_type.split("::")[-1]
updated_providers.append(
configure_single_provider(
provider_registry[api],
Provider(
provider_id=(f"{provider.provider_id}-{i:02d}" if len(plist) > 1 else provider.provider_id),
provider_id=(f"{pid}-{i:02d}" if len(plist) > 1 else pid),
provider_type=provider.provider_type,
config={},
),