LambdaInvoke: Warn legacy state type will be deployed with payloadResponseOnly #28950
Labels
@aws-cdk/aws-lambda
Related to AWS Lambda
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
p2
Describe the feature
After lots of digging around I realized that under the hood when someone adds
payloadResponseOnly: true
to theLambdaInvoke
class it will implement an older version of this state type.I had no idea until months later I saw the type
Task: lambda (legacy):invoke
in the console.Feature idea: It would be nice to have a warning in the IDE types or in the CLI console when doing a
synth
ordeploy
.Use Case
The use case would be to pre-warn folks like myself who don't go into the AWS console too often that adding this property will result in the non-optimized lambda invoke state type in their state machine. They can then quickly decide if that's ok or not for them.
It can also save folks lots of time debugging to try to figure out why this is happening. Example: I'm an AWS Hero and it took me 2hrs to finally figure this out.
Proposed Solution
No response
Other Information
Thanks for reading and for the great work on this project. 🚀
Acknowledgements
CDK version used
2.124.0
Environment details (OS name and version, etc.)
Mac OS Sonoma 14.2.1
The text was updated successfully, but these errors were encountered: