-
Notifications
You must be signed in to change notification settings - Fork 59
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
[ADAP-927] [Feature] Update boto3 to 1.29.* version #624
Comments
No objection to this! Would you like to open the PR? Certainly a low-hanging effort. If you're not interested, @soksamnanglim can pick it up. |
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Mila Page <[email protected]>
@dbt-labs/core-adapters We'll need to backport this to the appropriate minors (at least 1.6 as this affects 1.6.x) and release before moving this to Done. |
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Mila Page <[email protected]>
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Mila Page <[email protected]>
Backports |
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Kyu-Sang Kim <[email protected]>
* remove boto3 peg * add changelog entry * remove boto3 refs in tests + mark skip flakey test --------- Co-authored-by: Kyu-Sang Kim <[email protected]>
I linked the two backports and moved this into |
I've verified that |
Is this your first time submitting a feature request?
Describe the feature
Boto3 is pinned to the 1.26.* series, which is three major versions behind. This prevents use of updated awscli, boto3, botocore in conjunction with dbt-redshift
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: