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

the mentioned solution doesn't work, because the `aws.elasticache.ReplicationGroup` does not have an auto generated name, so pulumi unable to create it after deleted from the stack :disappointed:
` error: Plan apply failed: Error creating Elasticache Replication Group: ReplicationGroupAlreadyExists: Replication group with specified name already exists.`

Can you rename the `ReplicationGroup` to force a new one to be created?

I will try, but messed up the stack, I need to fix a few things first

now I created a postfix with the pulumi random package and added a keeper value to trigger the redis cluster replace if necessary, but it's a really hackish solution

hi <@UB3BGTV63>, I opened 2 issue for this:
<https://github.com/pulumi/pulumi-aws/issues/426>
<https://github.com/pulumi/pulumi-aws/issues/427>