Skip to content

Conversation

AllanZhengYP
Copy link
Member

@AllanZhengYP AllanZhengYP commented Jul 24, 2024

Description of changes

Merge the multibucket support to the storagebrowser branch. The only manual change is: 6e5b3c5

Issue #, if available

Description of how you validated changes

Unit test

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

ashika112 and others added 7 commits July 11, 2024 11:36
* update parseAmplifyOutput

* update bundle size

* address comments

* update bundle size
* update options and test
* update assertion error & download test
* update getUrl & getProp test
* update remove and list tests
* update multi-part tests
* update list & download test
* update more storage tests
* update bundle size
* address comments
* copy multibucket draft 1

* update copy with key and tests

* update the path route

* cleanup

* update bundle size

* address minor nits
@AllanZhengYP AllanZhengYP requested a review from ashika112 July 24, 2024 01:30
@AllanZhengYP AllanZhengYP force-pushed the storage-browser-sync-multi-buckets branch from 6b736e1 to 048ea00 Compare July 24, 2024 16:21
@AllanZhengYP AllanZhengYP marked this pull request as ready for review July 24, 2024 16:26
israx
israx previously approved these changes Jul 24, 2024
);
const { bucket: sourceBucket } = await resolveS3ConfigAndInput(amplify, {
path: input.source.path,
options: { ...input.source },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if u dont send in credentials provider as options will it not fallback to singleton usage here? should we just have it as options on both source and destination

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in 4f9f9d8

@AllanZhengYP AllanZhengYP requested a review from israx July 24, 2024 18:08
@AllanZhengYP AllanZhengYP merged commit d89cc27 into aws-amplify:storage-browser/main Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants