Add Google Drive and AWS S3 as a Remote Storage option #503
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
added 10 commits
March 25, 2025 19:10
cs7-shrey
changed the title
|
Hey @adamltyson @JoeZiminski, I know reviewing this PR wouldn't be feasible at the moment. But it would be great if you can try it out locally whenever you have time and let me know if it works correctly / any suggestions you'd have. No hurry at all, I understand if it takes a bit longer. |
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.
Description
This pull requests is a first version of Google Drive and AWS S3 integration in the datashuttle API and TUI.
What is this PR
Why is this PR needed?
What does this PR do?
This PR is to discuss the approach for implementing Google Drive and AWS S3 as a remote storage option.
References
Issue #407
How has this PR been tested?
This PR was manually tested in the Datashuttle's Python API and TUI. Comprehensive tests are yet to be written.
Is this a breaking change?
No
Does this PR require an update to the documentation?
Yes
Checklist: