Building and Deploying a Rust Lambda Function with Cross-Compiling and AWS CDK

[true stag]

https://www.youtube.com/watch?v=WxOma63Cx8Q by @subtle stratus

[gentle berry]

Hi @subtle stratus, I'm curious. Your first pipeline for building and deploying the lambda function is written using sync code, while the build image one is using async. Is that because they were authored by different teams?

[subtle stratus]

@gentle berry yeah you are right. We use the sync code because we have to execute it in the order. Build the image and then deploy it.

In the build image part we create a base image with rust and everything we need to cross-compile the application. So here we are free to do that async because we build the image for the different platforms/architecture.

[gentle berry]

Ah, I see, so there's a bit of a misunderstanding here. Just by using async/await it's not asynchronous on it's own. You need to use asynchronous features. You can read more about it in the "But aren't I using async?" section in https://github.com/dagger/dagger/issues/4766

@subtle stratus May I suggest you switch to using async only? 😅 I want to deprecate the sync version hopefully, but haven't created an issue yet.

[subtle stratus]

@gentle berry yeah of course. I would switch. So I will have a look on that and try to switch. Thank you for the information. It was not clear for me.

[gentle berry]

I'll add a section for how to convert in the deprecation issue. It's very simple, just add await on methods that return a coroutine (e.g., exit_code, stdout... coroutine = async def); add an async before any def that includes an await; add the async before with dagger.Connection. That's it. With only that, it'll still run in sequence (i.e., synchronous).