I also think that transfer operators should be put in origin package. Maybe
it is also worth to consider to make import available in “destination” for
example by import? This would make it easier for user to find a right
operator.
T.
On Sat, 21 Sep 2019 at 22:04, Felix Uellendall
wrote:
> In
In my opinion the source of the transfer operation is what matters - without
knowing the source you don‘t need to know where it can be transferred to.
So I prefer to put those „cross transfer“ operators to its source. For example:
GoogleApiToS3 -> gcp
Best Regards,
Felix
Sent from ProtonMail M
I like putting them with source.
On Sat, Sep 21, 2019, 12:57 PM Philippe Gagnon
wrote:
> Another way to resolve this could be to define a convention such that a
> "cross transfer" operator should belong to either the source or destination
> cloud provider's package.
>
> Personally though I do no
Another way to resolve this could be to define a convention such that a
"cross transfer" operator should belong to either the source or destination
cloud provider's package.
Personally though I do not see any technical issues with having a
"cross_transfer" package, but I don't find the name to rol
I have a question: Should we put all transfer operators between into
separate "cross_transfer" package ?
*Context:*
We had one unresolved point when we decided about AIP-21 - where to put
transfer operators between service providers. In the middle of implementing
it, it turned out that we need to
