-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
CDK does not add existing Cloudfront as trigger to Lambd@Edge? #20494
Comments
Update :- i do have code which was used while change cloudfront API's , could this be a problem
|
@jatinmehrotra , the CDK V1 is deprecated and we no longer provide updates on this.
Migration guide - https://docs.aws.amazon.com/cdk/v2/guide/migrating-v2.html I am closing this issue as its related to V1. Please feel free to reopen if you face the similar issue in CDK V2. |
|
Describe the bug
I am using CDK v1,
Whenever i am trying to update my Lambda@edge function, the Lambda@edge stack is created with function, lambda role but it does not add EXISTING Cloudfront distribution.
Expected Behavior
Ideally when i update my lambda code, the new lambda@edge stack should automatically have trigger as existing cloudfront distribution.
Current Behavior
After i update lambda code, CDK creates new lambda@edge stack which has iam role, but does not have cloudfront as trigger.
Reproduction Steps
Lambda@edge code
Cloudfront code
Possible Solution
Is it due to cdk v1?
Additional Information/Context
No response
CDK CLI Version
1.153
Framework Version
No response
Node.js Version
14.17.6
OS
macOS
Language
Typescript
Language Version
4.4.3
Other information
No response
The text was updated successfully, but these errors were encountered: