llama-stack/docs/resources
Ashwin Bharambe 09269e2a44
Enable sane naming of registered objects with defaults (#429)
# What does this PR do? 

This is a follow-up to #425. That PR allows for specifying models in the
registry, but each entry needs to look like:

```yaml
- identifier: ...
  provider_id: ...
  provider_resource_identifier: ...
```

This is headache-inducing.

The current PR makes this situation better by adopting the shape of our
APIs. Namely, we need the user to only specify `model-id`. The rest
should be optional and figured out by the Stack. You can always override
it.

Here's what example `ollama` "full stack" registry looks like (we still
need to kill or simplify shield_type crap):
```yaml
models:
- model_id: Llama3.2-3B-Instruct
- model_id: Llama-Guard-3-1B
shields:
- shield_id: llama_guard
  shield_type: llama_guard
```

## Test Plan

See test plan for #425. Re-ran it.
2024-11-12 11:18:05 -08:00
..
agentic-system.png moving rfc->docs 2024-09-18 16:54:24 -07:00
list-templates.png move openapi from rfcs->docs 2024-09-18 16:09:17 -07:00
llama-stack-spec.html Enable sane naming of registered objects with defaults (#429) 2024-11-12 11:18:05 -08:00
llama-stack-spec.yaml Enable sane naming of registered objects with defaults (#429) 2024-11-12 11:18:05 -08:00
llama-stack.png add llama-stack.png 2024-09-26 11:17:46 -07:00
model-lifecycle.png moving rfc->docs 2024-09-18 16:54:24 -07:00
prompt-format.png Add files via upload 2024-10-08 15:29:19 -07:00