Rust language support

[itmecho]

Are there any future plans to add rust language support?

[pgavlin]

Rust support is not something we have planned for the near future. However, community contributed support here would be welcome.

[Type1J]

As soon as Plumi has Rust support, I'm switching all of my Terraform to Plumi.

[d4h0]

I'm in the same boat. The lack of support for Rust is the main reason I don't use Pulumi.

[bionicles]

This would be legit

[jkelleyrtp]

Just bumping this - Rust binds very well into other languages and could be used to support nodejs, python, elixir, ruby, go, and more. It might be a good idea to support the the lowest level language and then just build every other interface on top.

[tmarkovski]

We'd love to integrate Pulumi into our CLI should Rust support be available. +1

[Type1J]

It looks as if Rust support would be well received. Does Pulumi have any interest in making this support happen, or do I need to role my own? I'm wrapping Terraform in Jake (Node.js based Make-like task runner). I'm going to convert that code to rust-script wrapping Terraform, but if Pulumi support is on the way, I'll wait.

[danmx]

It seems there is a check list what's required for a new language support. Should we Kickstart a community effort to get it? I'd be interested since now I'd have to write my personal projects' IaC in Go or Python but I'd love to switch to Rust.

[NickLarsenNZ]

@danmx what did you have in mind for how a community could collaborate on this? Discord or something?

I'm curious to see how macros can be used to reduce as much boiler-plate as possible. An example (adapted from aws-typescript the example):

use pulumi::{
    pulumi,
    aws,
    awsx,
}

#[pulumi::main]
fn stack() {
  // Create an AWS resource (S3 Bucket)
  let bucket = aws::s3::Bucket::new("my-bucket");
  
  // Export the name of the bucket
  #[output]
  let bucket_name = bucket.id;
}

Some more ideas over here in the readme: https://github.com/NickLarsenNZ/pulumi-language-rust

[Type1J]

Could outputs just be a serde_deriveed struct? Also, I'm assuming plumi::main is for an async runtime. I think most will try to used #[tokio:main], since 1 possible application with Pulumi is making a k8s style controller service, and most of those frameworks use tokio.

[NickLarsenNZ]

@Type1J, for sure - I think whatever reduces boiler plate so you can get on with the task.
It might be nice to be able to export outputs as you go, rather than saving them until the end.

As for #[pulumi::main], that was more to do with stripping away more boiler plate. I was imagining that macro making the main function async as well as bringing in Pulumi, or running the closure or something. I'd just seen how pulumi.Run had been called in a Go example.