Feature request to support generating CDK support as part of chalice package
Thanks for the feature request! To make sure I understand, you'd want chalice package to generate a CDK construct that you could then import/add to an existing CDK stack/app correct?
BTW, please feel free to 馃憤 the issue so we can gauge interest in this feature!
As a Chalice user, I want to integrate with the rest of my AWS CDK resources and assets that interact and are outside the self-contained Chalice workflow.
Thanks for the feature request! To make sure I understand, you'd want
chalice packageto generate a CDK construct that you could then import/add to an existing CDK stack/app correct?BTW, please feel free to 馃憤 the issue so we can gauge interest in this feature!
yup
Thanks for the feature request! To make sure I understand, you'd want
chalice packageto generate a CDK construct that you could then import/add to an existing CDK stack/app correct?BTW, please feel free to 馃憤 the issue so we can gauge interest in this feature!
It looks like 'cdk synth' is approximately similar in intent as 'chalice package'. In the current workflow, we would need to do these steps to make it work:
cdk synth -o stack which generates json files inside stack containing most of the stack outside of the lambdachalice package --merge-template stack/abc.json which produces a sam.json containing the full stack including the lambdaI feel that we should aim to simplify that interaction between 1 and 2. I would rather not use chalice package at all if there was a way of defining the Chalice stack with the CDK. One idea could be Chalice mixin class to inherit within the CDK or to support some of the composition methods within the CDK.
@devangmehta123 I though about the simplification you mentioned as well, and developed https://github.com/alexpulver/cdk-chalice library - would be glad to hear your thoughts. There is an example application using this approach at https://github.com/alexpulver/aws-cdk-sam-chalice/ (along with link to blog post with walkthrough).
Most helpful comment
Thanks for the feature request! To make sure I understand, you'd want
chalice packageto generate a CDK construct that you could then import/add to an existing CDK stack/app correct?BTW, please feel free to 馃憤 the issue so we can gauge interest in this feature!