Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions cli/azd/extensions/azure.ai.agents/internal/cmd/init.go
Original file line number Diff line number Diff line change
Expand Up @@ -1259,8 +1259,8 @@ func (a *InitAction) configureModelChoice(
}

modelConfigChoices := []*azdext.SelectChoice{
{Label: "Deploy new model(s) from the catalog", Value: "new"},
{Label: "Use existing model deployment(s) from a Foundry project", Value: "existing"},
{Label: "Deploy new model(s) (with new Foundry project)", Value: "new"},

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine with me, unless we want to complete pivot to "Create a new foundry project or use an existing one", and then "create a new model deployment or use an existing one" if users select to use an exisiting project. @therealjohn

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the right fix here is to decouple projects from models.

We also don't need to ask for a model unless its a resource defined in the agent manifest.

@v1212 can you pivot this to focus on that?

@v1212 v1212 May 21, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@trangevi @trangevi yes, I intended to decouple completely project selection/creating from model selection/creating in parallel, this PR is quick one to make existing flow easy to follow and avoid confuse.

I will work on a follow up PR to refactor in azd init, key changes will be like below, please suggest if any thoughts. feel free to leave this pr here as it can only help clarify before the refactor gets released.

? Select a Foundry project:

Use an existing Foundry project
Create a new Foundry project
--- If "Use an existing Foundry project" is selected ---
? How would you like to configure model(s) for your agent?
Use an existing model deployment
Deploy a new model from the catalog
Skip for now
--- If "Create a new Foundry project" is selected ---
? How would you like to configure model(s) for your agent?
Deploy a new model from the catalog
Skip for now

in total, 5 cases will be supported
if using existing project, then create/choose/skip model
if create new project, then create/skip model

{Label: "Use an existing Foundry project", Value: "existing"},
}

var modelConfigChoice string
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -491,8 +491,8 @@ func (a *InitFromCodeAction) createDefinitionFromLocalAgent(ctx context.Context)

// Ask user how they want to configure a model
modelConfigChoices := []*azdext.SelectChoice{
{Label: "Deploy a new model from the catalog", Value: "new"},
{Label: "Select an existing model deployment from a Foundry project", Value: "existing"},
{Label: "Deploy new model(s) (with new Foundry project)", Value: "new"},
{Label: "Use an existing Foundry project", Value: "existing"},
{Label: "Skip model configuration", Value: "skip"},
}

Expand Down
Loading