-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove legacy shell from test scripts #1404
Conversation
The legacy shell was only used in AWS authentication tests, so updating those gets rid of the last remaining use of the legacy shell. JAVA-4791
@blink1073 I'm getting a failure in the web identity variant, and could use some help debugging. |
This is how it was before, just missed it.
Finally took the blinders off and spotted it. We had previously been skipping web identity test using the built-in AWS credential provider, but when I copied the Evergreen configuration from the Go driver example I inadvertently removed the skipping logic. Added it back in second commit and tests are "passing" again. |
The legacy shell was only used in AWS authentication tests, so updating those gets rid of the last remaining use of the legacy shell. JAVA-4791
The legacy shell was only used in AWS authentication tests, so updating those gets rid of the last remaining use of the legacy shell. JAVA-4791
The legacy shell was only used in AWS authentication tests, so updating those gets rid of the last remaining use of the legacy shell. JAVA-4791 (cherry picked from commit 46fda2f)
The legacy shell was only used in AWS authentication tests, so updating those gets rid of the last remaining use of the legacy shell.
JAVA-4791