{AKS} Add framework for interactive AI agent tool #8990
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @mainred, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
microsoft-github-policy-service
bot
requested review from
FumingZhang,
yanzhudd,
yonzhan and
zhoxing-ms
mainred
force-pushed
the
aks-agent
branch
5 times, most recently
from
a6ff392 to
f00da46
Compare
mainred
changed the title
az aks agentaz aks agent
|
@mainred It's expected that members / contributors can trigger pipeline automatically. The current inefficient status is because of an ADO bug on permission detection. See bug ticket https://mseng.visualstudio.com/AzureDevOps/_workitems/edit/2272746 CLI team is also suffering from commenting |
|
@evelyn-ys @@yonzhan |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Hi @mainred |
github-actions
bot
added
the
release-version-block
mainred
changed the title
az aks agentaz aks agent
github-actions
bot
removed
the
release-version-block
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@FumingZhang please help merge this PR if there's no other changes required. |
mainred
changed the title
az aks agent
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
| :param refresh_toolsets: Refresh the toolsets status. | ||
| :type refresh_toolsets: bool | ||
| """ | ||
| with CLITelemetryClient(): |
There was a problem hiding this comment.
AKS wants to leverage its own monitoring to collect metrics more than cli startup as well as tool calling and token usages etc. in the future.
| action="store_true", | ||
| ) | ||
|
|
||
| # pylint: disable=line-too-long |
There was a problem hiding this comment.
May I ask why these lines of code need to be commented out? If the parameters should be removed, please delete them directly.
There was a problem hiding this comment.
We comment them out because these code will be introduced by one week or so later.
Currently we are under private preview to not expose this feature the user, unless the private preview looks good.
There was a problem hiding this comment.
Removing the agent subcommand from commands.py requires us to remove the parameters and helps to meet the requirement of style check. We want to keep as many code as possible though.
Keeping them here so that we can bring them back soon. If you are against from commenting so many code, I am fine to remove them directly.
There was a problem hiding this comment.
Got it. Just commenting them out temporarily is fine.
7 participants
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.