Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: protocol to send destinations to collaborators allowed to access them. #20

Closed
qascade opened this issue Apr 6, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@qascade
Copy link
Owner

qascade commented Apr 6, 2023

Description

Look at the Solution 3 spec doc.
Assumption: We have validated/compiled the transformation and defined who is allowed to get the generated output destination_tables.
We want that a output folder populated with destination_tables get generated under the respective collaborators package who has been prompted to receive the destination table.

So Create a server on dcr side and another server that will get go inside container.

Problem1: How do we send transformation from dcr side server to container server. And Container server triggers it on the Sql and receive. (Medium)
Problem2: Given destination_tables recieved by container server. How does container server makes sure that they reach to their respective destinations securly. (Hard)

@qascade qascade added the enhancement New feature or request label Apr 6, 2023
@qascade qascade changed the title feat: protocol to send destination_tables to collaborators allowed to access them. feat: protocol to send destinations to collaborators allowed to access them. Apr 17, 2023
@qascade qascade assigned tiklup11 and unassigned qascade Apr 17, 2023
@qascade
Copy link
Owner Author

qascade commented May 19, 2023

Closing this as not applicable in the latest release

@qascade qascade closed this as completed May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants