Fixes for default selection with azd up #247
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This template is referenced at the top of the AI-templates site and from the main 3 reference templates for coding in the AI Foundry portal.
However, running
azd up
and accepting whatever is the default location from the user is most likely to fail!, Leading customers into disappointment.This PR bring the initial changes for the infrastructure to make it work again. The changes to the sample
api
are still pending.Infra changes:
gpt-35-turbo
togpt-4o-mini
gpt-4-evals
-> Not sure what model to use to replace this one....hub.bicep
connection toAIServices
instead ofAzureOpenAI
-> Not sure if this is a breaking change...main.bicep
with the list of locations that supports Foundry projects + semantic ranker + content safetybicepparams
file and usingmain.parameters.json
to leverage azd's prompt for location (not supported from bicepparam).Missing changes:
gpt-4o-mini
and consolidate the repository name. I think it iscontoso-chat
, but there are references tocontoso-chat-openai-prompty