adding project-endpoint to init command #6596
Conversation
achauhan-scc
requested review from
JeffreyCA,
ZubaeyrMSFT,
hemarina,
kingernupur,
rabollin,
rajeshkamal5050,
saanikaguptamicrosoft,
tg-msft,
trangevi,
vhvb1989,
wbreza and
weikanglim
as code owners
There was a problem hiding this comment.
Pull request overview
This PR extends the fine-tuning extension’s init command to support initializing via an Azure AI Foundry project endpoint URL, alongside the existing ARM resource ID flow, and bumps the extension version to 0.0.12-preview.
Changes:
- Added new flags to
init(--project-endpoint/-e,--subscription/-s, renamed--projectto--project-resource-id/-p, changed--environmentshort flag to-n, and renamed--sourceto--working-directory/-w). - Implemented
parseProjectEndpointandfindProjectByEndpointplus new logic inensureEnvironmentto resolve a project from the endpoint, prompt for subscription, and populate AZURE_* environment values. - Updated version metadata in
version.txt,extension.yaml, andCHANGELOG.mdwith a new entry describing the endpoint support.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| cli/azd/extensions/azure.ai.finetune/version.txt | Bumps the extension version to 0.0.12-preview to reflect the new functionality. |
| cli/azd/extensions/azure.ai.finetune/internal/cmd/init.go | Adds endpoint-parsing and project-discovery logic, new flags (subscription, project-endpoint), and updates environment initialization to work with either project endpoint or ARM resource ID. |
| cli/azd/extensions/azure.ai.finetune/extension.yaml | Updates the extension manifest’s version to 0.0.12-preview to align with the code changes. |
| cli/azd/extensions/azure.ai.finetune/CHANGELOG.md | Adds a 0.0.12-preview changelog entry describing the new project-endpoint parameter. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| // Handle project endpoint URL - extract account/project names and find the ARM resource | ||
| if flags.projectEndpoint != "" { | ||
| accountName, projectName, err := parseProjectEndpoint(flags.projectEndpoint) | ||
| if err != nil { | ||
| return nil, fmt.Errorf("failed to parse project endpoint: %w", err) |
There was a problem hiding this comment.
With the new --project-endpoint and existing --project-resource-id flags, if a user specifies both, this branch will silently take precedence and ignore the resource ID. To avoid ambiguous behavior in the CLI API, consider validating that these two options are mutually exclusive (e.g., early in Run or at the top of ensureEnvironment) and returning a clear error when both are provided.
2 participants
This pull request adds support for specifying a project endpoint URL to the
initcommand in the Azure AI Foundry Fine Tuning extension. Users can now initialize their environment using either an ARM project resource ID or a project endpoint URL, improving flexibility and usability. The update includes new flag options, endpoint parsing, and logic to resolve project details from the endpoint.New project endpoint support:
--project-endpoint(-e) flag to theinitcommand, allowing users to specify the Azure AI Foundry project endpoint URL as an alternative to the ARM resource ID. [1] [2]parseProjectEndpointandfindProjectByEndpointfunctions to extract account and project names from the endpoint URL, search for the corresponding resources in Azure, and retrieve project details.Flag and parameter changes:
--projectflag to--project-resource-id(-p) and updated its description for clarity. Added new flags for--subscription(-s),--project-endpoint(-e), and changed--environmentshort flag from-eto-n.Other updates:
0.0.12-previewinextension.yaml,CHANGELOG.md, andversion.txt. [1] [2] [3]init.goto support the new endpoint-based workflow, including environment variable assignments and command argument construction. [1] [2]