This message was deleted.

sparse-intern-71089

12/14/2023, 8:41 PM

This message was deleted.

👀 1

little-cartoon-10569

12/14/2023, 9:09 PM

Not within Pulumi. To do this in pure Pulumi, you'd need to separate your resources into multiple projects.

little-cartoon-10569

12/14/2023, 9:09 PM

The normal way to achieve this is to use a machine cluster or container cluster, and let your cloud service manage it.

little-cartoon-10569

12/14/2023, 9:10 PM

E.g. in AWS, you'd use EKS, ECS or an ASG.

rhythmic-match-71423

12/14/2023, 9:25 PM

thanks, I can't use a cloud abstraction in this scenario

rhythmic-match-71423

12/14/2023, 9:26 PM

I was curious if a Dynamic Resource could wrap real resource(s) so I could inject locks around

update()

, but I haven't seen any examples of that

little-cartoon-10569

12/14/2023, 9:30 PM

No, I think the code that runs in dynamic resources runs in the deploy phase. Pulumi resources are created before that, when you're setting up state. You can use the Cloud service's normal APIs in a dynamic resource. Essentially re-implement the Pulumi resoruce.

little-cartoon-10569

12/14/2023, 9:31 PM

But it's likely that the best "pure" implementation would be to move the instances into their own project, separate from all the stuff they depend on. Put each instance in its own stack. And schedule the stack updates yourself. Or from an automation-api program.

rhythmic-match-71423

12/14/2023, 9:33 PM

yeah, though at that point pulumi isn't providing much value to the arrangement

little-cartoon-10569

12/14/2023, 9:57 PM

It isn't? That seems valuable to me. Scheduling logic is never provided by Pulumi. That's always provided by the cloud provider: AWS, Kubernetes, etc. If there's a need for scheduling here, it's Linode that's not meeting it. You can work around that via Pulumi's automation-api. But Pulumi isn't letting you down, in this instance.

rhythmic-match-71423

12/14/2023, 9:59 PM

Linode does have a Kubernetes abstraction, however, this usage can't depend on an abstraction like that

little-cartoon-10569

12/14/2023, 10:00 PM

But it could depend on a Linode feature equivalent to AWS's ASG. It's still not a Pulumi problem to solve.

rhythmic-match-71423

12/14/2023, 10:13 PM

Someone pointed out the

--parallel

flag which might be sufficient, if not enforced strictly.

little-cartoon-10569

12/14/2023, 10:14 PM

Ah yes, I haven't ever used that flag. Adding

--parallel 1

looks good.

little-cartoon-10569

12/14/2023, 10:15 PM

But I don't know if the API called by the Linode provider will block until the machine comes back. And once the API call returns, Pulumi will move onto the next bit 😞

rhythmic-match-71423

12/14/2023, 10:18 PM

ah, yes, it certainly won't block, good point... it really would require custom code I'll have to experiment with wiring up a lock system with Dynamic Resources

little-cartoon-10569

12/14/2023, 10:18 PM

Good luck!

rhythmic-match-71423

12/14/2023, 10:18 PM

thanks for your help

👍 1

3 Views

Open in Slack

Previous Next

Pulumi Community

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.