-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Can't set Lambda as ALB Target #17457
Labels
@aws-cdk/aws-elasticloadbalancingv2-targets
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
Comments
usman5251
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Nov 10, 2021
ryparker
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
Nov 10, 2021
blacha
added a commit
to linz/basemaps
that referenced
this issue
Nov 11, 2021
kodiakhq bot
added a commit
to linz/basemaps
that referenced
this issue
Nov 11, 2021
…fixed (#1962) See aws/aws-cdk#17457 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
nija-at
added
@aws-cdk/aws-elasticloadbalancingv2-targets
needs-triage
This issue or PR still needs to be triaged.
and removed
@aws-cdk/aws-lambda
Related to AWS Lambda
p1
effort/small
Small work item – less than a day of effort
labels
Nov 24, 2021
Duplicate of #17261 |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-elasticloadbalancingv2-targets
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
What is the problem?
Previously I was able to use the below stack to set Lambda Function as ALB target. Now it doesn't work
Now I get this error:
I was able to use a workaround and I think I know what the problem is, Please read Other Information
Reproduction Steps
This stack should be enough to reproduce error:
What did you expect to happen?
Creation of ALB with Lambda as its target.
What actually happened?
I get this error:
CDK CLI Version
1.132.0 (build 5c75891)
Framework Version
No response
Node.js Version
v16.11.0
OS
Manjaro
Language
Python
Language Version
Python 3.6
Other information
I had another project that used the same stack, Which used to work without any problems, Luckily I had the project with its Python Virtual Environment. I
pip freeze > requirements.txt
on that environment and used thatrequirements.txt
in the current project. All went well thenWorking Requirements.txt:
Not working requirements.txt:
I also found another issue, which I think is root cause of the issue. On running
cdk synth
, there is one major difference in outputoutput of
cdk synth
using latest dependencies (NOT WORKING):output of
cdk synth
using old dependencies:Notice NOT WORKING
cdk synth
output has TargetGroupAttributes, while WORKINGcdk synth
output don't.Please let me know if something is not clear.
The text was updated successfully, but these errors were encountered: