[BUG] The AzureFileClient.GetFilesAsync call fails when called with Vision purpose

[SergeyMenshykh]

Library name and version

Azure.AI.OpenAI 2.0.0-beta.2

Describe the bug

Calling AzureFileClient.GetFilesAsync method with the OpenAIFilePurpose.Vision purpose fails.

Expected behavior

The method call returns list of files with the Vision purpose if they exist or an empty collection if they don't.

Actual behavior

The method call fails with the exception:

• HTTP 400 (invalidPayload) Invalid value for purpose.
• StackTrace: ClientPipelineExtensions.ProcessMessageAsync(ClientPipeline pipeline, PipelineMessage message, RequestOptions options) AzureFileClient.GetFilesAsync(String purpose, RequestOptions options) FileClient.GetFilesAsync(Nullable1 purpose, CancellationToken cancellationToken) ClientCore.RunRequestAsync[T](Func1 request) line 170

Reproduction Steps

Create an instance of the AzureOpenAIClient class, get the file client, upload a file with Assistance purpose (not sure if it's important) and call the GetFilesAsync method with the Vision purpose:

var azureClient = new AzureOpenAIClient(endpoint, apiKey, options);

await azureClient.GetFileClient().UploadFileAsync(content, "test_content.txt", purpose: FileUploadPurpose.Assistants);

var files = await azureClient.GetFileClient().GetFilesAsync(purpose: OpenAIFilePurpose.Vision);

Environment

Windows 11 .NET8.0 Visual Studio 17.10.2

[github-actions[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

[trrwilson]

Thanks, @SergeyMenshykh! Great catch. The new vision purpose isn't yet supported by Azure OpenAI; you can track that in the REST documentation here: https://learn.microsoft.com/en-us/rest/api/azureopenai/files/upload?view=rest-azureopenai-2024-05-01-preview&tabs=HTTP&preserve-view=true#purpose

Service support work for image input (and Azure content safety integration) is underway and will work seamlessly via the API once it's available.