-
Notifications
You must be signed in to change notification settings - Fork 249
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 synth (v1.75.0) throws error with aws-lambda-step-function #108
Comments
Thanks @knihit, looking into it! |
@knihit Thanks for your patience. I tried recreating your code using a variant of the
Let me know if I'm missing anything with the config here! If so, could you please share more details around steps to reproduce and a larger code sample? Thanks! |
@hayesry , in the lambda function you defined, can you include the timeout propery as well and specify a 'Duration'. const lambdaFunctionProps = {
runtime: lambda.Runtime.NODEJS_10_X,
handler: 'index.handler',
code: lambda.Code.fromAsset(`${__dirname}/lambda`),
timeout: Duration.minutes(5)
}; |
@knihit - Added the
Let me know if I'm missing anything there? |
++ Current code is:
|
The fix for this bug is released in v1.79.0 |
I think the bug is still present: any time the
In the end I think the issue is that deep-diff and Duration are not compatible in the current state. |
When synthesizing a construct that uses aws-lambda-step-function, an error is thrown and synthesis fails. When looking at the stack trace, the root cause seems to be linked to the override warning that is published during synthesis. I can confirm that there were no issues until v1.73.0.
Reproduction Steps
A simple code to invoke the construct
Error Log
Looking at the stack strace, the error seems to be related to the following lines from core/lib
I suppressed the warning message using
export overrideWarningsEnabled=false
and the synthesis is successful.
Environment
Other
Full stack trace when running a unit test
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: