Adjust no_auth test expectation to address semver hazards failure
#4211
Conversation
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
2 tasks
landonxjames
approved these changes
Jul 15, 2025
|
A new generated diff is ready to view.
A new doc preview is ready to view. |
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.
Motivation and Context
This PR is a prerequisite for #4203.
Details
PR4203 has updated some of the
AuthSchemeIdstring values, which causes theno_authtest to fail in the semver hazards check. This happens because the inner string value forNO_AUTH_SCHEME_IDhas been modified fromno_authtonoAuth.To resolve this, this PR updates the test expectation so that it no longer depends on raw string values. Once this PR is merged and released from
aws-sdk-rust, PR4203 should pass the semver hazards check successfully.Also the test has been moved to
no_auth.rssince it is not specific to S3 Express; it was originally placed inexpress.rsbecause the issue was first discovered while investigating S3 Express behavior.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.