fix: Add support for passing authorization_scopes on routes with JWT authorizer #67
Conversation
This file contains hidden or 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
…ute types must all match for conversion to map' error
jschilperoord
changed the title
antonbabenko
pushed a commit
that referenced
this pull request
Apr 1, 2022
### [1.6.1](v1.6.0...v1.6.1) (2022-04-01) ### Bug Fixes * Add support for passing authorization_scopes on routes with JWT authorizer ([#67](#67)) ([c2b8d6b](c2b8d6b))
|
This PR is included in version 1.6.1 🎉 |
|
Amazing work, works like a dream! Thank you all. |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Description
Make it possible to pass the authorization_scopes as a comma separated string on the integration level. Passing it as a set of string like the AWS resource expects makes the variable validation fail with a " attribute types must all match for conversion to map" as also described here
Motivation and Context
Due to missing documentation on the AWS provider the authorization_scopes parameter was being ignored. The docs have been updated as seen here
This fixes issue
Breaking Changes
No. This is an optional parameter
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request