fix(static-push): use doesBucketExistV2 ref: #24698 #27367
Merged
Conversation
This file contains 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
jdotcms
approved these changes
Jan 18, 2024
jcastro-dotcms
approved these changes
Jan 18, 2024
|
0.0% Coverage on New Code
0.0% Duplication on New Code
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
7 tasks
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.
AWSS3Storage
Use a newer method to validate Bucket since some regions require signature v4, and this method takes care of it.
AWSS3PublisherTest
Amazon framework changed the response when the Access Key is not valid, now it returns an error, so the test is no longer valid since we're sending an invalid Key: