Any best practices for reducing resources under management? Our usage has grown significantly - which is great we love pulumi! - but our bill has also grown significantly - which is not as great!
(as a side note: I don’t love the convoluted pricing. I wish somewhere would just tell me “$x per resource under management per month” instead of making me convert from credits to nanocents to hours to months to dollars.)
04/11/2023, 12:01 PM
Your best bet will be to reach out to a sales rep or your customer success manager and begin negotiating price.
Alternatively, you need to become less reliant on the pulumi service.
04/11/2023, 12:30 PM
We (Pulumi) will be announcing some new functionality soon that might (depending on your situation) make it easier to find resources that are no longer needed/no longer in use (which may help).
04/11/2023, 12:43 PM
As a customer, the resource-based pricing model for the Pulumi service doesn't make sense. I think long-term it's doing more to hurt Pulumi's adoption.
As an organization, the more we use deploy infrastructure with Pulumi, the more it will cost us.
This encourages us to 1) Be more selective about when to use Pulumi. 2) Not invest in the Pulumi service or any features offered by it.
This effectively limits our use of the Pulumi Service to a state-hosting service, further devaluing it and encouraging migration out of the service. The recent changes to the S3 state backend is a nice investment in treating migrating projects in and out of the service as a first-class use case (which will likely be a necessary step for customers looking to reduce their Pulumi costs).
Against our existing projects, the orphaned resource tool sounds like finding change in the couch.
04/11/2023, 7:02 PM
What @millions-furniture-75402 said resonates with me. We invested a lot in moving everything over to Pulumi/IAC. I still think that was a good decision, and for what we’re paying today we’re getting a lot of value.
But now that we’ve scaled up and I’ve gotten my first “real” bill, it does create some awkward additional friction to future projects. I’ve added a line in our project proposal documents about estimated resource use, what that will cost us, and how it might scale up over time.