Update Azure.AI.OpenAI to 2.1.0 and add tests

[manvkaur]

This pull request introduces several breaking changes, dependency updates, and enhancements to the Azure Functions OpenAI Extension and its Java library. Key updates include renaming properties and classes for better clarity, adding managed identity support, and updating dependencies. Additionally, a new unit test project has been added, and documentation has been updated to reflect these changes.

Breaking Changes and Enhancements:

• Renamed properties in bindings (model to chatModel and embeddingsModel, connectionName to searchConnectionName and storeConnectionName) and renamed ChatMessage to AssistantMessage. [1] [2] [3] [4] [5] [6]
• Updated Java library annotations, Assistant and Semantic Search bindings to include new configuration options (e.g., temperature, topP, maxTokens) and replaced EmbeddingsOptions with a List<String> for input in EmbeddingsContext. [1] [2]

New Features:

• Introduced aiConnectionName for managed identity support in bindings like AssistantPost, EmbeddingsStore, SemanticSearchand TextCompletion. [1] [2]
• Additional configuration options for AI service connections, including managed identity and fallback to environment variables.
• Added experimental isReasoningModel property to support reasoning models. [1] [2]

Dependency Updates:

• Updated Azure.AI.OpenAI to version 2.1.0 and azure-ai-openai to version 1.0.0-beta.16. [1] [2]

Testing and CI Enhancements:

• Added a new unit test project WebJobsOpenAIUnitTests to the solution and included it in the CI pipeline for build and test coverage. [1] [2]
• Add Samples Tests for:
  1. Embeddings
  2. Semantic Search
  3. Text Completion
• Add Unit Tests for:
  1. OpenAI Client Factory
  2. Assistant Service

Documentation Updates:

• Updated README.md to reflect new requirements (e.g., .NET 8 SDK, Azurite) and detailed configuration options for AI service connections. Added examples for managed identity and configuration sections. [1] [2]

File and Class Renaming:

• Renamed ChatMessage to AssistantMessage in the Java library, Worker and WebJobs csproj, including corresponding updates to fields and methods. [1] [2] [3] [4]
• Removed reference to preview package Microsoft.Azure.WebJobs.Script.Abstractions and deleted unused BuiltInFunctionsProvider.cs

Issues Resolved:

1. Allow configuring properties like Max Token,Top_P etc in Assistant Post #104
2. https://github.com/Azure/azure-functions-pyfx-planning/issues/395
3. https://github.com/Azure/azure-functions-pyfx-planning/issues/164
4. https://github.com/Azure/azure-functions-pyfx-planning/issues/269

Performance impact:

1. Latency in first client creation as it has moved from start up to binding, later calls can retrieve from cache if exists.

Will add more test coverage in upcoming PRs.

Next PR:

• Python decorators - fix: update decorators for openai extension azure-functions-python-library#280
• Python samples - Update java, python samples for param renames #156
• Java samples (dependent on publish of java library part of current PR) - Update java, python samples for param renames #156

[Copilot]

Copilot reviewed 135 out of 140 changed files in this pull request and generated no comments.

Files not reviewed (5)

• OpenAI-Extension.sln: Language not supported
• java-library/pom.xml: Language not supported
• samples/assistant/csharp-legacy/AssistantSample.csproj: Language not supported
• samples/assistant/csharp-ooproc/AssistantSample.csproj: Language not supported
• samples/assistant/java/extensions.csproj: Language not supported

Comments suppressed due to low confidence (3)

java-library/src/main/java/com/microsoft/azure/functions/openai/annotation/textcompletion/TextCompletion.java:56

• [nitpick] Consider updating the associated Javadoc to reference 'chatModel' instead of 'model' so that the documentation aligns with the new property name.

String chatModel() default "gpt-3.5-turbo";

java-library/src/main/java/com/microsoft/azure/functions/openai/annotation/embeddings/EmbeddingsContext.java:14

• Review the change from using EmbeddingsOptions to List for input to ensure that downstream processing is compatible with the new type; verify any related transformation logic has been updated accordingly.

private List<String> input;

java-library/src/main/java/com/microsoft/azure/functions/openai/annotation/assistant/AssistantMessage.java:28

• [nitpick] Update the Javadoc comment for the constructor to clearly describe the purpose of the 'toolCalls' parameter, ensuring consistency with previous documentation for the renamed property.

public AssistantMessage(String content, String role, String toolCalls) {

[aishwaryabh]

Left a few nit comments but looks good overall!

[TsuyoshiUshio]

Hi @manvkaur

I'd like to understand the context why you changed the name as breaking change.

Renamed properties in bindings (model to chatModel and embeddingsModel, connectionName to searchConnectionName and storeConnectionName) and renamed ChatMessage to AssistantMessage. Updated managed identity support via the aiConnectionName property for Azure OpenAI

I've got the answer from the author.

I wanted to create a base class, AssistantBaseAttribute, to serve as the foundation for AssistantAttribute, SemanticSearchAttribute, and TextCompletionAttribute.

One of the child classes uses two models - ChatModel and EmbeddingsModel, so I aimed to keep them distinct.

Additionally, a new property, AIConnectionName, was introduced for Azure OpenAI connection settings. Therefore, I changed the connection name property for EmbeddingStoreAttribute to storeConnectionName to clearly indicate it is for the embedding store. Similarly, I renamed it to searchConnectionName to specify it is for the search resource connection.

[manvkaur]

Hi @manvkaur

I'd like to understand the context why you changed the name as breaking change.

Renamed properties in bindings (model to chatModel and embeddingsModel, connectionName to searchConnectionName and storeConnectionName) and renamed ChatMessage to AssistantMessage. Updated managed identity support via the aiConnectionName property for Azure OpenAI

I wanted to create a base class, AssistantBaseAttribute, to serve as the foundation for AssistantAttribute, SemanticSearchAttribute, and TextCompletionAttribute.

One of the child classes uses two models - ChatModel and EmbeddingsModel, so I aimed to keep them distinct.

Additionally, a new property, AIConnectionName, was introduced for Azure OpenAI connection settings. Therefore, I changed the connection name property for EmbeddingStoreAttribute to storeConnectionName to clearly indicate it is for the embedding store. Similarly, I renamed another connectionName to searchConnectionName to specify it is for the search resource connection.