This message was deleted.

sparse-intern-71089

10/04/2022, 2:53 PM

This message was deleted.

✅ 1

fast-river-57630

10/04/2022, 3:09 PM

the XY problem is "moving a pulumi object with lots of dependencies from codebase A to codebase B while keeping references to vpc.id in A entact" I'm going to try to upgrade to 3.40.2... nope.

billowy-army-68599

10/04/2022, 3:19 PM

@fast-river-57630 your type token is wrong

Copy code

super("...", "my-vpc", {}, opts);

billowy-army-68599

10/04/2022, 3:19 PM

it needs to be

Copy code

super("foo:index:vpc"

fast-river-57630

10/04/2022, 3:20 PM

my type token is right. I just removed the specifics from my example

fast-river-57630

10/04/2022, 3:20 PM

I tried pkgcompanynameVpc

billowy-army-68599

10/04/2022, 3:22 PM

ah got it

fast-river-57630

10/04/2022, 3:35 PM

i'm assuming pulumi.ComponentResources just dont have providers (i tried setting provider in opts) so when the dependency graph code is resolving a provider reference for a replaced object and that object is component resource it just throws up in the pulumi binary. not sure if you can trace the errors in the pulumi binary (+%v???) Found a workaround, will post. Thank you!

fast-river-57630

10/04/2022, 3:36 PM

use a dynamic resource with a stub?? it did work: https://gist.github.com/sheenobu/a58297508055a3e4c83aee1b5f38432e I purposefully made create error out since this is just for stubbing out migrated objects!

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.