This message was deleted.
# generals
sparse-intern-71089
07/10/2020, 7:26 PMThis message was deleted.
h
hallowed-rain-9096
07/10/2020, 7:27 PMthat sounds like possibly your Typescript code that creates
xxx-policyt
thousands-train-20124
07/10/2020, 7:28 PMIf that was the case wouldn't the same error occur even on the first deployment? The first deployment works perfectly. If I destroy and redeploy it works perfectly
g
gentle-diamond-70147
07/10/2020, 9:05 PMThat error looks like it's coming from the provider itself. Are you operating on the correct stack? Or has some other process created a resource with the same name?
t
thousands-train-20124
07/11/2020, 1:19 AMI always use --stack option, so the correct stack should be picked up by pulumi. No other process or manual intervention creates stacks. BTW, this only happens when I try to update after I have made any changes to the typescript code. I happens specifically with s3 buckets, dynamodb tables, roles and policies. For dynamodb tables still the update seems to carry on, but will roles and policies pulumi throws exception and exits. This is a very undesirable behavior.
thousands-train-20124
07/11/2020, 1:57 AMJust some additional info, using the following command to update the stack same as creating it
pulumi up --stack <stack> --yesthousands-train-20124
07/11/2020, 5:35 AMSo it seems like without auto naming pulumi is unable to update without destroying the stack. Updates should work without auto naming as well and should not throw EntityAlreadyExists exception.
thousands-train-20124
07/11/2020, 1:20 PMOne last problem, when I do an update facing an issue with CloudFront distribution
creating CloudFront Distribution: CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.g
gentle-diamond-70147
07/12/2020, 5:04 PMCan you share some of the code that is causing this? This is definitely not normal or expected behavior.
t
thousands-train-20124
07/18/2020, 9:27 AMI apologize for the delay in response, actually I had to move to auto names instead of static names to fix these issues.
102 Views