-
-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for CloudFront functions #167
Add support for CloudFront functions #167
Conversation
bc2d51b
to
28c0315
Compare
This follows the naming of Terraform's AWS provider. Lambda@Edge functions are "lambda functions", whereas CloudFront functions are simply "functions".
1d96fcc
to
ac97daa
Compare
@@ -462,6 +470,14 @@ resource "aws_cloudfront_distribution" "default" { | |||
lambda_arn = lambda_function_association.value.lambda_arn | |||
} | |||
} | |||
|
|||
dynamic "function_association" { | |||
for_each = lookup(ordered_cache_behavior.value, "function_association", []) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a lookup for backwards compatibility
I've tested this by deploying my own distribution with an attached function 👍 |
By adding this, shouldn't we also update the aws provider pin to > 3.41.0 ? It would be nice to link the docs for the |
Thanks for the feedback, done both! |
/test all |
thank you! |
what
This follows the naming of Terraform's AWS provider. Lambda@Edge
functions are "lambda functions", whereas CloudFront functions are
simply "functions".
references