fix(api): create RequestDecorator in interceptor #1623
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
sktimalsina
approved these changes
Jan 6, 2022
sdhuka
reviewed
Jan 6, 2022
sdhuka
approved these changes
Jan 6, 2022
|
With the change, I am able to successfully configure the AWSApiPlugin and make API calls (post, get, etc.). |
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.
Issue #, if available: #1606
Description of changes: When configuring the AWSApiPlugin for REST with
AMAZON_COGNITO_USER_POOLSas the authorization type, configuration fails due to trying to fetch auth tokens when creating theRequestDecorator. This PR moves the creation of theRequestDecoratorinside the interceptor so the auth tokens aren't retrieved when configuring the AWSApiPlugin.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.