This message was deleted.

sparse-intern-71089

11/25/2020, 3:38 PM

This message was deleted.

green-school-95910

11/25/2020, 7:12 PM

I'm not entirely sure, you can create Random resources to test it with a local stack

green-school-95910

11/25/2020, 7:13 PM

I think it will be recreated since the resource urn will change.

little-cartoon-10569

11/25/2020, 7:37 PM

You can use aliases to avoid this. Specifically, the

parent

property.

👍 1

little-cartoon-10569

11/25/2020, 7:38 PM

So if you're changing the parent of a ComponentResource from

this

this.newParent

, you'd have something like

Copy code

new MyComponentResource(name, {}, {
  parent: this.newParent,
  aliases: [{
    parent: this
  }]
});

👍 1

little-cartoon-10569

11/25/2020, 7:41 PM

And for the special case where you're moving something with no parent to a parent, use

pulumi.rootStackResource

as the parent alias.

future-nail-59564

11/27/2020, 10:09 PM

👍

future-nail-59564

11/27/2020, 10:11 PM

I also did a quick test and, if the parent name is not explicitly included in the child’s name, then changing parent has no effect, as long as the new parent component is of the same type as the old one (because that is part of the child’s URN).

green-school-95910

11/28/2020, 2:23 AM

That is good to know

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