Release v1.0.6 #161
Merged
Release v1.0.6 #161
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
fridgepoet
requested review from
sarahzinger and
kevinwcyu
and removed request for
a team
|
|
|
|
|
Code coverage report for PR #161
|
vickyyyyyyy
approved these changes
Jul 12, 2022
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 #160
Error occurs when connecting to us-gov-west-1 region.
Error message:
"message":"error executing query: InvalidClientTokenId: The security token included in the request is invalid\n\tstatus code: 403Investigation:
Redshift v1.0.5 includes grafana-aws-sdk v0.10.2 which included the following change: grafana/grafana-aws-sdk@fb33415
Redshift v1.0.2 uses grafana-aws-sdk v0.9.1 which was the last Redshift version without that change.
Downgrading to Redshift plugin version 1.0.2 resolved the above error.
Proposed solution:
Because Redshift v1.0.2 is connecting successfully for the original issue reporter, we think that releasing Redshift with a fixed grafana-aws-sdk will resolve the issue (as it did for the same problem in Athena).