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

[FEATURE REQ] Service discovery with Azure services #47255

Open
erwinkramer opened this issue Nov 19, 2024 · 2 comments
Open

[FEATURE REQ] Service discovery with Azure services #47255

erwinkramer opened this issue Nov 19, 2024 · 2 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Extensions ASP.NET Core extensions feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Milestone

Comments

@erwinkramer
Copy link

Library name

Any

Please describe the feature.

Would be cool if we can leverage Service discovery in .NET with the Azure SDK. This way we can streamline the usage of Azure endpoints.

So for example doing this, where you can set on 3 levels:

services.ConfigureAzureClientDefaults(clients =>
{
    clients.AddServiceDiscovery(); // Turn on service discovery by default for all clients: largest scope
});

services.AddAzureClients(builder =>
{
    builder.AddServiceDiscovery(); // Turn on service discovery by default for all clients: smaller scope
    
    builder.AddBlobServiceClient(serviceUri: new Uri("https://myBlobService")).ConfigureOptions( options =>
    {
        options.AddServiceDiscovery(); // Turn on service discovery by default for all clients: smallest scope
    }
    
    );
});
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 19, 2024
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. Extensions ASP.NET Core extensions and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Nov 20, 2024
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Nov 20, 2024
@jsquire
Copy link
Member

jsquire commented Nov 20, 2024

//fyi: @annelo-msft, @m-redding

@jsquire
Copy link
Member

jsquire commented Nov 20, 2024

Hi @erwinkramer. Thank you for your suggestion. I'm not sure how well service discovery maps to the Azure SDK packages, but we'll take a deeper look into things and give this consideration.

@jsquire jsquire added this to the Backlog milestone Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Extensions ASP.NET Core extensions feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Development

No branches or pull requests

2 participants