llama-stack-mirror/llama_stack/providers/remote
Ben Browning b69bfab019 fix: Some missed env variable changes from PR 2490
Some templates were still using the old environment variable
substition syntax instead of the new one and were not getting
substituted properly.

Also, some places didn't handle the new None vs old empty string ("")
values that come from the conditional environment variable
substitution.

This gets the starter and remote-vllm distributions starting again,
and I tested various permutations of the starter as chroma and
pgvector needed some adjustments to their config classes to handle the
new possible `None` values. And, I had to tweak our `Provider` class
to also handle `None` values, for cases where we disable providers in
the starter config via environment variables.

This may not have caught everything that was missed, but I did grep
around quite a bit to try and find anything lingering.

Signed-off-by: Ben Browning <bbrownin@redhat.com>
2025-06-26 17:27:17 -04:00
..
agents test: add unit test to ensure all config types are instantiable (#1601) 2025-03-12 22:29:58 -07:00
datasetio refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
eval refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
inference refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
post_training refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
safety refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
tool_runtime refactor(env)!: enhanced environment variable substitution (#2490) 2025-06-26 08:20:08 +05:30
vector_io fix: Some missed env variable changes from PR 2490 2025-06-26 17:27:17 -04:00
__init__.py impls -> inline, adapters -> remote (#381) 2024-11-06 14:54:05 -08:00