llama-stack-mirror/llama_stack
Charlie Doern 236a670fc1 fix: separate build and run provider types
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>
2025-07-25 14:34:06 -04:00
..
apis feat(auth): API access control (#2822) 2025-07-24 15:30:48 -07:00
cli fix: separate build and run provider types 2025-07-25 14:34:06 -04:00
distribution fix: separate build and run provider types 2025-07-25 14:34:06 -04:00
models chore(api): add mypy coverage to chat_format (#2654) 2025-07-18 11:56:53 +02:00
providers feat: implement chunk deletion for vector stores (#2701) 2025-07-25 10:30:30 -04:00
strong_typing chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
templates fix: separate build and run provider types 2025-07-25 14:34:06 -04:00
ui chore(deps): bump form-data from 4.0.2 to 4.0.4 in /llama_stack/ui (#2898) 2025-07-24 21:24:56 -04:00
__init__.py export LibraryClient 2024-12-13 12:08:00 -08:00
env.py refactor(test): move tools, evals, datasetio, scoring and post training tests (#1401) 2025-03-04 14:53:47 -08:00
log.py fix: use logger for console telemetry (#2844) 2025-07-24 16:26:59 -04:00
schema_utils.py feat(auth): API access control (#2822) 2025-07-24 15:30:48 -07:00