-
Notifications
You must be signed in to change notification settings - Fork 189
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
bugfix(AWS SSO Format): #195
Conversation
…ow teller to use the new SSO format with minimal changes, mostly just needed to upgrade the aws sdk v2 packages for aws
@stvnksslr can you please check the conflicts? |
Thanks for taking a look fixed |
regression in unit tests / linting is caused by this breaking change introduced in a minor version from aws we either need to pin before the change or rework the test invocation pretty frustrating how they rolled this out. Not sure why i didnt run into it originally. |
Ok everything's fixed except the vendor file for the new aws versions @kaplanelad in the past you guys wanted only core contributors to touch that directory. |
@stvnksslr from what i see the ci fails on linting. |
@kaplanelad linter error was import related should be sorted now. |
Related Issues
#177
Description
fix for the aws SSO new format, this will allow teller to use the new SSO format with minimal changes, mostly just needed to upgrade the aws sdk v2 packages for aws
Motivation and Context
the aws sdk packages used in teller are quite old and are starting to lose compatibility with aws itself. Likely as a security tool there are a number of package sub dependencies that have now been upgraded.
How Has This Been Tested?
Items of note
there are still a few scattered deprecation warnings in the aws files, will get to these when I have time but I dont think they are needed to be fixed to close out this issue.
Checklist