Add custom header block into distribution origin block #108
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
* add custom_origin_headers variable Use case : LambdaEdge does not allow environment variables, so if you want use multiple distributions to call same lambdaEdge function you can use a custom_headers block into distribution to pass some variables that the lambda function can read and execute some logic depends of a distribution. * Updated README.md * Update variables.tf * Update main.tf * Updated README.md * Executed 'terraform fmt'
homeria-repo
requested review from
jamengual and
RothAndrew
and removed request for
a team
|
/test all |
|
/rebuild-readme |
|
/test all |
|
/test bats |
|
/test all |
|
/test all |
Gowiem
approved these changes
Nov 27, 2020
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.
what
add custom_origin_headers variable
Updated README.md
Update variables.tf
Update main.tf
Updated README.md
Executed 'terraform fmt'
why
Use case : LambdaEdge does not allow environment variables, so if you want use multiple distributions to call same lambdaEdge function you can use a custom_headers block into distribution to pass some variables that the lambda function can read and execute some logic depends of a distribution.
references
https://stackoverflow.com/questions/54828808/aws-lambdaedge-nodejs-environment-variables-are-not-supported#:~:text=Environment%20variables%20are%20not%20supported%20by%20Lambda%40Edge%20as%20specified,with%20CloudFront%20Origin%20Custom%20Headers.