misc: correct test assertion and @Ignore it
#1239
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
|
lauzadis
added
the
no-changelog
|
A new generated diff is ready to view. |
0marperez
approved these changes
Mar 1, 2024
ianbotsf
approved these changes
Mar 1, 2024
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.
The previous assertion for
X-Amz-Security-Tokenis not consistently working across all developer environments. That header is only added by some credentials providers, so it's not a safe assertion to make.This PR updates the test to the "correct" state and adds
@Ignoreuntil #1236 is resolved.Issue #
Description of changes
This change is required to ensure E2E tests pass on all developer environments
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.