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

If you want the new instances out there now.. I'm pretty sure you'll just need to resize your ASG min/max/desired capacity sizes to launch some new servers which will use the new LT then drop the size back down to whatever you originally had it set to. The termination policy should delete the oldest instances first.

Right, but I don't _think_ I can do that all in *one* run right? I would have to have two separate steps in the stack, but they would have to use the same resource name. And if you have two of the same resource name in the same stack, you get an error.

I'm trying to automate a release process to do this.

The api to do this is only exposed to cloud formation. If you want this feature, you’ll need to define a cloud formation stack with Pulumi.
Alternatively, you can run this on your nodes: 

<https://github.com/deitch/aws-asg-roller/blob/master/README.md|https://github.com/deitch/aws-asg-roller/blob/master/README.md>

<@UCWG26BH7> or anyone, is there an equivalent to "Create_before_replace"?

Looks like if you set `DeleteBeforeReplace` explicitly to false, it creates the replacement before deleting the old.