feat(infra): d.i. config and provider in in-memory provider service #4887
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
Cliftonz
approved these changes
Nov 27, 2023
Cliftonz
merged commit c2ea177
into
nv-3197-move-provider-selection-to-workflow-and-cache-in-memory
1 check passed
Cliftonz
deleted the
nv-3225-di-the-provider-and-config-into-inmemoryservice
branch
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.
What change does this PR introduce?
Dependency injection of the provider and its config in InMemoryProviderService.
Why was this change needed?
This allows configuration overriding and will allow multiple instances of the same provider with different configurations.
Other information (Screenshots)