Why isn't it possible to define a config (fallbacks, load balancing, etc.) or link to a config id in a prompt template? If you can select a single virtual key you should also be able to select a config that is used. In my opinion both features make only sense if combined, else you still have to override some stuff in code and cannot use the UI-based prompt management to iterate on prompt configurations properly. Or am I missing something?
we never thought of this usecase for prompt templates, intially the ability to select virtual key was more from a perspective of the user needing a key to make a call and not to attach a key to the prompt template
Ah, that explains some current limitation. 🙂 So the virtual key selection was just build to test the prompt? But why is in this case the virtual key used in prompt completions if not overwritten?
