-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(cloudfront): custom EdgeFunction aliases clash #13237
Labels
@aws-cdk/aws-cloudfront
Related to Amazon CloudFront
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
in-progress
This issue is being actively worked on.
p1
Comments
arjunnaha
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 23, 2021
github-actions
bot
added
the
@aws-cdk/aws-cloudfront
Related to Amazon CloudFront
label
Feb 23, 2021
arjunnaha
changed the title
(cloudfront, lambda): short issue description
(cloudfront, lambda): custom EdgeFunction aliases clash
Feb 23, 2021
nija-at
changed the title
(cloudfront, lambda): custom EdgeFunction aliases clash
(cloudfront): custom EdgeFunction aliases clash
Feb 25, 2021
njlynch
added
effort/small
Small work item – less than a day of effort
p1
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Mar 1, 2021
njlynch
added a commit
that referenced
this issue
Mar 1, 2021
Attempting to add two EdgeFunctions to the same stack, and then giving both the same alias (e.g., 'prod', 'live') results in an ID conflict. This is because the aliases are being added to the scope of the shared EdgeFunction stack, rather than the scope of the Function itself. fixes #13237
Thanks for the bug report! Fix posted for review. |
mergify bot
pushed a commit
that referenced
this issue
Mar 1, 2021
Attempting to add two EdgeFunctions to the same stack, and then giving both the same alias (e.g., 'prod', 'live') results in an ID conflict. This is because the aliases are being added to the scope of the shared EdgeFunction stack, rather than the scope of the Function itself. Note - Also took the opportunity to simplify one of the integ tests to deploy to a single distribution. fixes #13237 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
cornerwings
pushed a commit
to cornerwings/aws-cdk
that referenced
this issue
Mar 8, 2021
…13324) Attempting to add two EdgeFunctions to the same stack, and then giving both the same alias (e.g., 'prod', 'live') results in an ID conflict. This is because the aliases are being added to the scope of the shared EdgeFunction stack, rather than the scope of the Function itself. Note - Also took the opportunity to simplify one of the integ tests to deploy to a single distribution. fixes aws#13237 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-cloudfront
Related to Amazon CloudFront
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
in-progress
This issue is being actively worked on.
p1
When using multiple CloudFront
EdgeFunction
's with custom aliases, the physical names conflict.Reproduction Steps
What did you expect to happen?
Both EdgeLambda functions would be generated with unique stack/physical names.
What actually happened?
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: