Fix key-based credentials for redshift copy #2016
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
|
@dlstadther, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ddaniels888, @rantav and @steenzout to be potential reviewers. |
|
Thanks! :) |
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.
Fixes breaking changes to key-based credentials from PR #1962
Description
Mistakenly merged PR using word
aws_secret_keyrather thanaws_secret_access_key. Caused RedshiftInternalErrorwhen using key-based credentials during Redshift copy.Motivation and Context
Fixes breaking PR
Have you tested this? If so, how?
Ran fine for me this morning.