test(middleware-sdk-s3): use crypto.randomUUID for E2E test bucket names - #8088
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
trivikr
force-pushed
the
test-e2e-middleware-region-redirect
branch
from
June 8, 2026 19:48
5e5e6b5 to
d470a49
Compare
trivikr
marked this pull request as ready for review
June 8, 2026 19:48
kuhe
approved these changes
Jun 8, 2026
8 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
Internal JS-6960
Description
Replace 2-character random ID with crypto.randomUUID to avoid
BucketAlreadyExists errors from S3's global bucket namespace collisions
during concurrent CI runs. Also remove unnecessary STS dependency,
redundant deleteBucket pre-cleanup, and headBucket sanity check.
Testing
CI
Checklist
*.integ.spec.ts) or E2E tests.@public,@internaltags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.