Migrating to AWS SDK V3 | Use AWS SDK V3 In Unit Tests (namespace_auth, bucketspace, bucketspace versioning) #7461
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.
Explain the changes
Implementation of AWS SDK V3 (without wrapper) in unit tests:
listObjects
would not haveContent
as an empty array,deleteObjects
with no error would not have an emptyErrors
array, etc.).Issues: Fixed #xxx / Gap #xxx
upload
was not migrated to AWS SDK V3 (and still using AWS SDK V2).Testing Instructions:
The tests run as a part of the CI.
namespace_auth, bucketspace
make test
bucketspace versioning
make root-perm-test