feat: delegate Foundry project setup from agents - #9561
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 20 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Hi @Hui Miao (@huimiu). Thank you for your interest in helping to improve the Azure Developer CLI experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
|
Hi @Hui Miao (@huimiu). Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass. |
Why this is needed
Agents and Projects currently both participate in Foundry project setup. That makes ownership unclear and lets project-owned state be changed from two places.
Approach
Keep Agent definitions, Agent deployments, and workflows in
azure.ai.agents, while sending project-owned initialization and deployment inputs toazure.ai.projectsthrough the versioned input-only delegated contract. Existing Agent commands continue to own the Agent lifecycle.Scope
This draft contains the Agents-side delegation, adoption updates, tests, and documentation. Projects implementation changes are in the prerequisite drafts.
Dependency
This draft is based on #9560. After that PR is merged and its base branch is deleted, GitHub can retarget this PR to
main.