TestHost - Client ability to use IHostConfigurator to align w/ Silo functionality #8454
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ReubenBond
approved these changes
Jun 1, 2023
|
Thank you! I have also found the need for this and have implemented it in one of my (otherwise unrelated branches). LGTM |
|
Rebased & will merge soon. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to align client / silo host building capabilities while building a
TestClusterUse Case
In some use cases, a test application is attempting to set up a common configuration source between client / silo but is dependent on the
HostBuilderContextin order to do so. An example would be trying to mirror default .NET behavior for app settings files, env variables, etc.The silo configurator mechanism has hooks to hook directly into the
IHostBuilderinstance itself and do more robust customizations.By aligning the client side logic w/ the silo logic, end users can have common, shared code for configuring their
TestClusterMicrosoft Reviewers: Open in CodeFlow