No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

hey all, I would have thought we'd have a <http://fly.io|fly.io> provider by now but it's not looking good. is there a reason why? they are a premium cloud provider. is there someone else I should be using? I'm looking to deploy bytewax workloads for realtime data processing

I'm thinking of maybe getting into kubernetes to deploy dynamic/scalable workloads. are many people doing that?

<@U03CLBPHR0D> this is one created by my colleague <@U033KKRC6HY>, though not yet published in our Registry:
<https://github.com/dirien/pulumi-fly>

The “community” run provider if fly is dead: <https://github.com/fly-apps/terraform-provider-fly/issues/255>

There are some forks flying around and I am happy to switch to them,

I saw this too, I think it’s actually from the fly team themselves. The message at the top of the read me says not to use it

I found this “surprising” from <http://Fly.io|Fly.io> not provide their user a “Non- CLI” way of deploying workload, tbh.

I’ve actually just done the EKS tutorials from Pulumi docs and it wasn’t anywhere near as difficult as I thought it would be, so I’m moving all my services off of fly and onto EKS

I think fly is more for people who aren’t familiar with devops / IaC

some very interesting replies in that issue you linked <@U033KKRC6HY> - i think fly will lose a cohort of customers because of the choice to drop the terraform support

that might be ok with them though, because when I searched the fly community forums, I found very few people talking about terraform/iac