feat: add keyed Dataverse client registration - #9
Merged
Conversation
Copilot
AI
changed the title
[WIP] Add named Dataverse client registration to AddDataverseClient API
feat: add named keyed Dataverse client registration
Jun 20, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds named Dataverse client registration on top of the existing
AddDataverseClient()API using native keyed DI, enabling multiple independently configured clients (for examplesource/target) in the same app. The unnamed registration path remains unchanged and isolated from the named path.API surface: named
AddDataverseClientoverloadsAddDataverseClient(string name, Action<DataverseClientOptions> configureOptions)AddDataverseClient(string name, IConfiguration configuration)DI wiring: separate keyed registration path
AddNamedDataverseClientCore(string name)inServiceCollectionExtensions.ServiceClientIOrganizationServiceAsync2viaClone()Factory support for named options
ServiceClientFactory.CreateNamed(IServiceProvider, string name).IOptionsMonitor<DataverseClientOptions>.Get(name)to resolve named options.Create(IServiceProvider)unchanged.Test coverage for named behavior
ServiceClientFactory.CreateNamedbehavior (default/custom credential, deferred connection)Example usage: