This message was deleted.

sparse-intern-71089

10/21/2021, 8:51 PM

This message was deleted.

millions-journalist-34868

11/04/2021, 4:01 PM

Anyone knows how to solve that ? @tall-librarian-49374?

powerful-football-81694

11/04/2021, 4:24 PM

@millions-journalist-34868 you typically do this using Invoke calls.

powerful-football-81694

11/04/2021, 4:24 PM

Here’s one example from my code (string values obscured)

powerful-football-81694

11/04/2021, 4:25 PM

This example gets a reference to an existing KeyVault instance, that lives in a resource group in another subscription.

powerful-football-81694

11/04/2021, 4:26 PM

Then you can simply use

keyVault.Id

to refer to this vault, as an input, when creating other resources.

powerful-football-81694

11/04/2021, 4:27 PM

If your other resource is in the same subscription as your deployment is targeting, you can skip the

InvokeOptions

argument and the

Provider

object.

powerful-football-81694

11/04/2021, 4:27 PM

Hope that helps.

millions-journalist-34868

11/04/2021, 4:33 PM

That's awesome. Exatly what I was looking for. I will try that, thanks @powerful-football-81694!

powerful-football-81694

11/04/2021, 4:34 PM

No problem

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