Adds capabilities for components to implement connectivity testing #335
Conversation
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
Jeffail
force-pushed
the
connectivity-test
branch
from
47dcc28 to
f8abe98
Compare
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 the capability for individual components to implement a connectivity test, which can be used by downstream tooling to test the validity of configs without actually consuming and processing data.
This ended up being a much larger body of work than anticipated because I totally forgot just how deeply it is assumed within the engine that components that are instantiated will always be consuming. In order to work around this I have decoupled the initial handshake between components (where channels are exchanged) and the actual triggering of async connections and consumption of data.
In order to execute these connectivity tests there are new APIs within public/service that allow tools to create streams or build resources and then call connectivity tests on them without (or before) subsequently activating them.