-
Notifications
You must be signed in to change notification settings - Fork 251
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
fix (CloudFrontToS3 - use cloudfront function instead of lambda@edge) #272
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@@ -50,7 +49,7 @@ export interface CloudFrontToS3Props { | |||
|
|||
export class CloudFrontToS3 extends Construct { | |||
public readonly cloudFrontWebDistribution: cloudfront.Distribution; | |||
public readonly edgeLambdaFunctionVersion?: lambda.Version; |
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.
Good riddance to this! :-)
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 now a breaking change, isn't it? Although it seems extremely unlikely that a customer has used this property.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue #, if available: 295
Description of changes:
Use CloudFront function instead of lambda@edge for CloudFrontToS3 construct
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.