Service task connector delegate #225
Merged
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
burnettk
approved these changes
Sep 16, 2022
|
Kudos, SonarCloud Quality Gate passed! |
danfunk
approved these changes
Sep 16, 2022
essweine
approved these changes
Sep 16, 2022
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 is a change to give the consumer more control over how service task requests are executed. Previously service tasks could execute any class with an execute method - now the consumer of the library can provide a delegate to handle a given request. The backend currently routes requests through a local connector proxy, but a delegate could also communicate with a docker container, return dummy data, etc.
Wanted to go ahead and get this up since I have backend changes that depend on it.