Mike Osterhout

I would also like to voice my support for using `code: lambda.Code.fromAsset(...` in custom cdk resources. I have a similar use case as @shishkin for adding additional s3 trigger functions...

I plan to use more and more cdk as well but figure I can still just use it within amplify. But if I continue to run into hurdles like this...

I can report that `@aws-cdk/aws-lambda-nodejs` has the same "Parameters must have values" issue, unfortunately.

I raised this issue(https://github.com/aws/aws-cdk/issues/18090) with `aws-cdk` since what looked to be a promising `addEventNotification` function didn't seem to work with imported resources.

It seems like layout provider could just be a function that receives an index and is expected to return the dimensions like `(index: number) => Dimensions`. Maybe I am missing...

I am wondering how this would work when using something more declarative like react-query or swr? In those cases the data would be provided more like this where data would...

I am also facing this issue. Currently looking at using a custom image to rule out if maybe something is off with the live update to latest. Interestingly, if I...

adding to backend build commands `npm i -g @aws-amplify/cli` did up being a valid workaround for me.

I have a related question. When using `AMPLIFY_DIFF_BACKEND` can we still use `amplifyPush --simple` as part of the backend build? I get the sense that there can't be any commands...

I should follow up, if we can't use amplifyPush --simple as part of the build command with AMPLIFY_DIFF_BACKEND how should we go about deploying backend resources conditionally?