You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current approach is to use one AI Service per model. It simplifies the e2e experience when folks don't need to think about connections of services and just list the models to deploy.
For this issue, we want to support the default case of just listing the models in azure.yaml as a way to define all models to the same connection/service.
And then, introduce the schema for modeling more than one connection if folks want to do that.
The text was updated successfully, but these errors were encountered:
kristenwomack
changed the title
[Ai Compose] Support many model deployments for AI Service
[AI Compose] Support many model deployments for AI Service
Mar 5, 2025
Current approach is to use one AI Service per model. It simplifies the e2e experience when folks don't need to think about connections of services and just list the models to deploy.
For this issue, we want to support the default case of just listing the models in azure.yaml as a way to define all models to the same connection/service.
And then, introduce the schema for modeling more than one connection if folks want to do that.
The text was updated successfully, but these errors were encountered: