Skip to content

Conversation

WhitWaldo
Copy link
Contributor

Description

Today, configurations are set using the following precedence:

  1. Direct values
  2. IConfiguration
  3. Environment variables
  4. Default constants

This PR cleans up some of how all this works and simplifies it, registering a named HttpClient as well as adding support for configuration from IOptions giving us a new order of precedence:

  1. IOptions
  2. Direct values
  3. IConfiguration
  4. Environment variables
  5. Default constants

This gives us more flexibility and includes another best practice from the ASP.NET Core stack.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

…n with DaprHttpClientOptions, then values from IConfiguration, then environment variables, then constants for additional support.

Signed-off-by: Whit Waldo <[email protected]>
@WhitWaldo WhitWaldo added this to the Future milestone Jun 21, 2025
@WhitWaldo WhitWaldo self-assigned this Jun 21, 2025
@WhitWaldo WhitWaldo requested review from a team as code owners June 21, 2025 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant