refactor: create distributions from DataFlowManager
transfer types
#3669
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 this PR changes/adds
Makes
Catalog
'sDistribution
list being built by the knowledge of theDataFlowManager
, because that's where the supported transfer types knowledge is stored.This is the
DataFlowController
details:ProviderPush
will get the distributions out of theDataPlaneInstance
s registered on the connector and associate them with thePUSH
flow typeConsumerPull
for the moment will only return a singleHttp-PULL
type, in the future it will be able to provide other pull mechanism as well (ref. docs: decision record about Transfer type #3637)Why it does that
interoperability
Further notes
Linked Issue(s)
Closes #3631
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.