Add support for Assets
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Add support for AWS CDK Assets in the AWS Adapter.
Could make use of implementing a custom synthesizer that is passed to the AWS CDK Stack.
This issue is about a first iteration and does not need full support for any Asset to be closed, create follow-up issues as needed.
References
One of the best aspects of the CDK is the high level Lambda abstractions, especially NodejsFunction. I'd been hoping for something like it in CDKTF directly, but supporting the CDK's existing construct would also be a big win.
Wanted to call out how Pulumi tackled this: https://github.com/pulumi/pulumi-cdk/blob/main/src/stack.ts
Basically mapped the underlying Pulumi's own notion of assets, with the caveat that it still leans on the CDK's Bootstrap Stack to provide a staging ground for S3 Assets and ECR images. Possibly an approach that could partially unblock this?