https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
d
Hmm but I don’t want to recreate the 
ComponentResource
that I’m trying to delete
I want to replace the 
ComponentResource
(which contains a 
route53.Record
) with a new 
route53.Record
that conflicts
My new record is dependent on waiting for the old record to finish deleting
b
so you're not updating the same resource, you're creating a new one?
d
Yeah, I have a website on S3 in my component resource with a CNAME pointing to that S3 bucket. I want to delete the s3 bucket, the CNAME, etc. and replace it all with a webflow website…
I ended up splitting the deployments into phases, but it just led to more downtime
First commit was to delete the old resource, run the update… wait… then add the new code and run the update
b
if you're adding a new resource, I think this is the only way
can you update the existing one instead of creating a new one?
d
For your specific case (moving the dns record), you could use Alias. This will tell pulumi you've moved the code, and it'll run an update as needed instead of a delete + create. A short guide on this: https://www.pulumi.com/blog/cumundi-guest-post/
d
hmm so the 
ComponentResource
is a custom resource I created to set up a Route53/S3/CloudFront http redirect on a TLD. It’s a set of 8 related AWS resources. The new thing I want to create is a single A record
I can’t update the existing resource because it’s buried within my 
ComponentResource
20 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by