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

Hi Graham, this is unfortunately an issue with CloudFormation. you'll need to get your cloudformaiton stack into a state where it can be updated

Thanks, <@UCWG26BH7>. The stack is now in the ROLLBACK_COMPLETE state. Normally, when dealing directly with CloudFormation (using a self-crafted CF template), it would be possible to update the stack at this point. But seems Pulumi doesn't want to?

this appears to be an artifact of this issue in the terraform provider:
<https://github.com/hashicorp/terraform-provider-aws/issues/5194>

I see. At the moment, all I can do is destroy the stack completely and re-create it from scratch, whenever this happens. Maybe I'll check out the new aws-native provider, as that doesn't seem to go through CloudFormation.

<@U02EN6MP63H> are you using the awsx method of creating an ASG? you can create an ASG without using that resource

Yes, I'm creating a awsx.ecs.Cluster and then calling the createAutoScalingGroup method on that.

that is an opinionated mechanism to create autoscaling groups via CFN. it was chosen because CFN allowed instance refreshes on asgs

there's nothing stopping you using the aws autpscaling group resource and avoiding cfn altogether:
<https://www.pulumi.com/registry/packages/aws/api-docs/autoscaling/group/>