This message was deleted.

sparse-intern-71089

10/20/2021, 3:28 PM

This message was deleted.

swift-intern-18856

10/20/2021, 3:50 PM

I can refactor things, but leave the

{ parent: this }

on the resource options out ... this means that the dependency isn't established which kind of defeats the point. I'm not sure why simply establishing the dependency on a logical component grouping would cause the engine to want to delete the existing resources

swift-intern-18856

10/20/2021, 3:51 PM

This seems like weird behavior, nothing else depends on my new component group, it's just a logical grouping for the benefit of clarity.

freezing-van-87649

10/20/2021, 4:01 PM

need to set an alias: https://www.pulumi.com/blog/cumundi-guest-post/

❤️ 1

freezing-van-87649

10/20/2021, 4:03 PM

they go over that scenario in the blog post:

Copy code

const serviceAccountSecondCustomerKey = new gcp.serviceAccount.Key("ServiceAccountSecondCustomerKey",
    {
        serviceAccountId: serviceAccountSecondCustomer.email
    },
    {
        parent: serviceAccountSecondCustomer,
        aliases: [
            { parent: pulumi.rootStackResource }
        ]
    }
);

swift-intern-18856

10/20/2021, 4:10 PM

awesome!! thank you, that's so helpful, much appreciated

👍 1

freezing-van-87649

10/20/2021, 4:16 PM

very welcome

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