Feature/eas llm setup

[alex3267006]

---

Related command

This pull request introduces major improvements to the AKS Agent extension, focusing on simplifying LLM model setup and management for users. The most significant change is the addition of the new az aks agent-init command, which enables interactive configuration of LLM providers and models, removing the need for manual environment variable setup. Documentation and help text have been updated to reflect these changes, and new backend modules have been added to support provider selection and configuration management. There are also code changes to ensure configuration consistency and prevent conflicts.

User Experience and CLI Improvements

• Added the new az aks agent-init command, allowing users to interactively add and configure LLM models for AKS troubleshooting. This command saves model configurations locally, supports multiple providers, and guides users through the setup process.
• Updated documentation in README.rst and CLI help to highlight the new workflow: users no longer need to set environment variables manually, and can easily select or switch models using --model or --config-file.

Configuration Management and Validation

• Introduced LLMConfigManager (llm_config_manager.py) for robust loading, saving, and retrieval of LLM model configurations, ensuring the last used or specifically selected model is used by default.
• Added provider registry and interactive selection logic in llm_providers/__init__.py, making it easy for users to choose among Azure, OpenAI, Anthropic, Gemini, and other compatible providers.

Provider Support and Validation

• Added new provider classes for Azure, OpenAI, OpenAI-Compatible, Gemini and Anthropic, each with schema-based parameter validation and live connection testing to ensure correct configuration before use.

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.json automatically.
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.

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @alex3267006,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[microsoft-github-policy-service]

@alex3267006 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

[Copilot]

Pull Request Overview

This PR introduces major improvements to the AKS Agent extension, focusing on simplifying LLM model setup and management. The key change is the addition of the az aks agent-init command for interactive LLM configuration, eliminating the need for manual environment variable setup.

• Interactive LLM model configuration through az aks agent-init command
• Support for multiple providers (Azure, OpenAI, Anthropic, Gemini, OpenAI-compatible) with validation
• Configuration management system with local storage and model selection capabilities

Reviewed Changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
commands.py	Added new agent-init command
custom.py	Implemented aks_agent_init function and configuration management logic
agent/agent.py	Added configuration conflict prevention
agent/llm_config_manager.py	New configuration manager for LLM settings
agent/llm_providers/*.py	Provider classes with validation and connection testing
tests/latest/*.py	Test coverage for new functionality
_help.py	Updated help text and examples
README.rst	Updated documentation to reflect new workflow

[Copilot]

Corrected spelling of 'compatiable' to 'compatible'.

Suggested change

	class OpenAICompatiableProvider(LLMProvider):
	name = "openai_compatiable"
	class OpenAICompatibleProvider(LLMProvider):
	name = "openai_compatible"

[Copilot]

Corrected spelling of 'compatiable' to 'compatible'.

[Copilot]

Corrected spelling of 'compatiable' to 'compatible'.

[Copilot]

The endpoint 'openai/responses' appears incorrect. Azure OpenAI chat completions endpoint should be 'openai/deployments/{deployment-id}/chat/completions'. Consider using the correct endpoint pattern.

Suggested change

	url = urljoin(api_base, "openai/responses")
	url = urljoin(api_base, f"openai/deployments/{model_name}/chat/completions")

[Copilot]

The payload structure is incorrect for Azure OpenAI chat completions. It should include 'messages' array with role/content structure, not 'input' field. Consider using the correct payload format: {'messages': [{'role': 'user', 'content': 'ping'}], 'max_tokens': 16}.

Suggested change

	payload = {"model": model_name,
	"input": "ping", "max_output_tokens": 16}
	payload = {
	"model": model_name,
	"messages": [{"role": "user", "content": "ping"}],
	"max_tokens": 16
	}

[github-actions]

Hi @alex3267006

Release Suggestions

Module: aks-agent

• Please log updates into to src/aks-agent/HISTORY.rst
• Update VERSION to 1.0.0b5 in src/aks-agent/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema