Welcome to the fourth devlog for the WASM/Rust support for Pulumi! This week, I focused on improving provider versioning and spent time exploring the long-term vision for the project. Here’s what’s new:
Provider Version Support
Until now, we hadn’t set the proper provider version when calling Pulumi. While this didn’t throw an error, it caused the newest installed provider to be used by default. Since providers can introduce incompatible changes between versions, this behavior could lead to subtle bugs.
This issue has now been resolved. The provider glue code generated for version X will now explicitly request version X from Pulumi during execution, ensuring compatibility and reducing the risk of unexpected errors.
Future of the Project
This week, I spent a lot of time reflecting on the future direction of this project. (In fact, I created a few tickets to explore this further).
While WASM is an exciting target and has allowed me to design a constrained Pulumi execution engine, I’m now considering expanding the scope to include a native library. My goal is to create something akin to Amazon’s CRT—a library that supports both languages with C FFI and WASM-only languages. This approach would allow the project to serve a broader range of use cases and developers.
That's all for this week's updates!. As always, feedback is welcome—let me know your thoughts or if you run into any issues!
Top comments (0)