This message was deleted.

sparse-intern-71089

01/02/2019, 1:59 PM

This message was deleted.

cold-coat-35200

01/02/2019, 3:33 PM

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 😞

error: Plan apply failed: Error creating Elasticache Replication Group: ReplicationGroupAlreadyExists: Replication group with specified name already exists.

white-balloon-205

01/02/2019, 7:52 PM

Can you rename the

ReplicationGroup

to force a new one to be created?

cold-coat-35200

01/02/2019, 8:01 PM

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

cold-coat-35200

01/03/2019, 9:21 AM

I can rename the replicationGroup

cold-coat-35200

01/03/2019, 9:22 AM

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

cold-coat-35200

01/07/2019, 4:56 PM

hi @white-balloon-205, I opened 2 issue for this: https://github.com/pulumi/pulumi-aws/issues/426 https://github.com/pulumi/pulumi-aws/issues/427

58 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.