llama-stack-mirror/llama_stack
Dinesh Yeduguru 0850ad656a
unregister for memory banks and remove update API (#458)
The semantics of an Update on resources is very tricky to reason about
especially for memory banks and models. The best way to go forward here
is for the user to unregister and register a new resource. We don't have
a compelling reason to support update APIs.


Tests:
pytest -v -s llama_stack/providers/tests/memory/test_memory.py -m
"chroma" --env CHROMA_HOST=localhost --env CHROMA_PORT=8000

pytest -v -s llama_stack/providers/tests/memory/test_memory.py -m
"pgvector" --env PGVECTOR_DB=postgres --env PGVECTOR_USER=postgres --env
PGVECTOR_PASSWORD=mysecretpassword --env PGVECTOR_HOST=0.0.0.0

$CONDA_PREFIX/bin/pytest -v -s -m "ollama"
llama_stack/providers/tests/inference/test_model_registration.py

---------

Co-authored-by: Dinesh Yeduguru <dineshyv@fb.com>
2024-11-14 17:12:11 -08:00
..
apis unregister for memory banks and remove update API (#458) 2024-11-14 17:12:11 -08:00
cli Add a verify-download command to llama CLI (#457) 2024-11-14 11:47:51 -08:00
distribution unregister for memory banks and remove update API (#458) 2024-11-14 17:12:11 -08:00
providers unregister for memory banks and remove update API (#458) 2024-11-14 17:12:11 -08:00
scripts Add a test for CLI, but not fully done so disabled 2024-09-19 13:27:07 -07:00
templates Update provider types and prefix with inline:: 2024-11-12 12:54:44 -08:00
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00