feat: make projects own project authoring - #9928
Conversation
|
Azure Pipelines: Successfully started running 3 pipeline(s). 19 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
azure.ai.projects PR buildNote This is an unsigned development build. Install it only if you trust this PR. Install the extension: azd ext install "https://azuresdkartifacts.z5.web.core.windows.net/azd/extensions/pr/9928/azure-ai-projects.zip"
|
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Summary
azd ai project initas the canonical projects-owned project authoring command while retainingproject addfor compatibility.$refprotections, environment values, and rollback behavior during ownership migration.Why this is needed and why this approach was chosen
The projects extension must own the
azure.ai.projectservice block so other extensions can delegate project and deployment authoring without duplicating service-specific logic. This change exposes a stable projects-owned entry point and a strict file-based handoff contract while reusing the existing initialization and deployment reconciliation paths. Reuse keeps legacy Foundry manifests, existing project flows, conflict handling, and rollback behavior consistent instead of introducing a second implementation.Scope
This draft covers the projects-side ownership API. The agents extension will adopt this contract in a follow-up change.
Validation
go test ./... -count=1incli/azd/extensions/azure.ai.projectsgo build ./...incli/azd/extensions/azure.ai.projects