[WIP] patch (website): [refresh] port ChatUI from basic and use new Foundry (new) API#87
Conversation
ckittel
left a comment
ckittel
left a comment
There was a problem hiding this comment.
Got to the review today. Can you and I sync tomorrow? I think some of my questions might just be best answered via a call.
| # Persist the agent | ||
| az rest -u $FOUNDRY_AGENT_URL -m "post" --resource "https://ai.azure.com" -b @chat-with-bing-output.json |
There was a problem hiding this comment.
Can you help me (not the learner here) understand the shift that is happening from "Deploy" to "provision/persist" -- what's the distinction mean? Can it still be "Deploy" but use a term like "unpublished" or something?
There was a problem hiding this comment.
Ah! Reading ahead, it feels like we are maybe doing something more like "Publish agent definition" with the idea that the compute for it comes later.
| | :information: | You’ve just persisted a new versioned agent in Foundry AI Agent Service, including its instructions, tools, and model. The platform has stored a canonical agent definition in the `enterprise_memory` database, making the agent addressable, executable and ready for evaluation. At this stage, the agent is available for validation and has the unpublished state. | | ||
| | :-------: | :------------------------- | | ||
|
|
||
| 1. Publish the the Agent |
There was a problem hiding this comment.
I'm worried about the Persist/publish terms here. Maybe you and I can sync for a few minutes tomorrow and work through terms here.
| name: 'baseline-chatbot-agent' | ||
| properties: { | ||
| agents: [ | ||
| { | ||
| agentName: 'baseline-chatbot-agent' | ||
| agentVersion: agentVersion | ||
| } | ||
| ] | ||
| displayName: 'baseline-chatbot-agent' |
There was a problem hiding this comment.
We use baseline-chatbot-agent as a name here in this file six times. It might be nice to have them be different, where possible. That'll help someone who might be looking at API responses or the portal understand which name maps to what as a FK or as route information or as display text.
Co-authored-by: Chad Kittel <chad.kittel@gmail.com>
ferantivero
force-pushed
the
patch/538619_port-basic-website
branch
from
14eece2 to
679a81d
Compare
2 participants
WHY
as part of our changes to the RA, we noticed it'd be great to experiment with the prompt-based agent publishing process from the RI. Publishing promotes an agent from an evaluation asset into a managed Azure resource with a dedicated endpoint, independent identity, and governance capabilities. This way our RI is better aligned to a Foundry production instance narrative.
WHAT
TEST
Test outside the vnet
