Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClientModel: Provide API for indicating which service operation a request will be sent to #42652

Open
annelo-msft opened this issue Mar 12, 2024 · 2 comments
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. System.ClientModel Base Core library
Milestone

Comments

@annelo-msft
Copy link
Member

One proposal is to add a string OperationName property on PipelineMessage. This issue tracks the work to determine the best approach to expose.

@annelo-msft annelo-msft added Client This issue points to a problem in the data-plane of the library. Azure.Core System.ClientModel Base Core library labels Mar 12, 2024
@annelo-msft annelo-msft added this to the 2024-04 milestone Mar 12, 2024
@joseharriaga joseharriaga modified the milestones: 2024-04, 2024-05 Mar 28, 2024
@joseharriaga
Copy link
Member

This is needed to be able to support Azure OpenAI on top of OpenAI.

@annelo-msft
Copy link
Member Author

@joseharriaga, would it be possible to provide a little more detail here, to help connect the dots across Azure OpenAI and OpenAI clients? Today, Azure clients don't use the PipelineMessage type in System.ClientModel, although that may or may not change with the Azure.Core 2.0 integration work stream. Would this API be called from within an Azure client, or somehow used to to integration across Azure/other clients?

@pallavit pallavit modified the milestones: 2024-05, 2024-06, Backlog May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. System.ClientModel Base Core library
Projects
None yet
Development

No branches or pull requests

3 participants