feat: support authorization_type and authorizer_id on routes #17
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
Adds support for setting
authorization_type
andauthorizer_id
on theaws_apigatewayv2_route
resource, like so:Motivation and Context
This module is helpful but limited by the lack of support for custom authorizers. This commit isn't perfect - it requires you to create an
aws_apigatewayv2_authorizer
independently, and then reference the id, but it's also immediately useful. If this isn't sufficient to merge, please let me know what you'd like to see in a commit and I'll see if I can match those expectations.Defaults are set to what
aws_apigatewayv2_route
expects ("NONE", and null respectively).Breaking Changes
None that I know of, but I haven't committed to these modules before, so merger beware!
How Has This Been Tested?
I tested this on a private source repository, and successfully deployed more or less the above example. I also tested deploying without these new parameters, successfully (observing authorization_type being set to NONE and authorizer_id being set to null).