-
Notifications
You must be signed in to change notification settings - Fork 482
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
Support connection name-based configuration for Azure components #5827
Conversation
9f23492
to
fb751a4
Compare
playground/AzureFunctionsEndToEnd/AzureFunctionsEndToEnd.Functions/MyHttpTrigger.cs
Outdated
Show resolved
Hide resolved
Test Log
|
Yeah, I pulled a goofy pushing this commit without testing locally 🙊 We'll have to figure out how to inject the Functions-specific
|
BindSettingsToConfiguration(settings, configSection); | ||
BindSettingsToConfiguration(settings, configSection.GetSection(connectionName)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we only doing this for Azure client libraries? Shouldn't we be doing it for all, so they are consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Capturing offline discussion, we'll do this for all integrations but prioritizing Azure components and dependencies for Functions in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is getting pretty close. Just a few more comments.
playground/AzureFunctionsEndToEnd/AzureFunctionsEndToEnd.ApiService/Program.cs
Outdated
Show resolved
Hide resolved
src/Aspire.Hosting.Azure.Functions/AzureFunctionsProjectResourceExtensions.cs
Show resolved
Hide resolved
7b30329
to
fe0b889
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking really good. I'm going to approve it now, but obviously we will need to resolve conflicts and get CI green. Assuming no more material changes are made, this is ready to ship IMO.
fe0b889
to
1504c91
Compare
Description
This pull request adds support for named configuration providers to Azure components and updates resource types that implement
IResourceWithAzureFunctions
config to inject values into configuration model.Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore
to version2.0.0-preview1
to use newFunctionsWebApplicationBuilder
implementation so we can take advantage ofIHostApplicationBuilder
-based extension methods for integrations.IResourceWithAzureFunctionsConfig
to inject named configuration values into environment variables.AzureComponent
to support binding settings from named configuration providers.Checklist
<remarks />
and<code />
elements on your triple slash comments?Microsoft Reviewers: Open in CodeFlow