This message was deleted.

sparse-intern-71089

09/29/2021, 4:57 PM

This message was deleted.

bored-table-20691

09/29/2021, 4:58 PM

In general you should avoid creating resources and exports in apply

echoing-librarian-76448

09/29/2021, 5:00 PM

I do try to avoid it but there are times when I need a string value of a

pulumi.StringOutput

that I haven't found another way to access without

.ApplyT

echoing-librarian-76448

09/29/2021, 5:01 PM

you can see in the example that I'm trying to get a newly created VNet ID so I can build the subnet info. I wasn't been able to get the subnet ID directly

echoing-librarian-76448

09/29/2021, 5:22 PM

Is there a way to get a specific subnet's ID directly, even if it's a

pulumi.StringOutput

type? I could refactor our code to not need the plain string if it's possible.

bored-table-20691

09/29/2021, 7:49 PM

Which provider are you using?

lemon-agent-27707

09/30/2021, 1:00 AM

Exporting values from within apply is not supported and will not work.

👍 1

lemon-agent-27707

09/30/2021, 1:02 AM

You can accomplish the same thing by running an apply, returning the value you want to export, and exporting the output returned by the apply. Some pseudocode:

Copy code

idOutput := val.Apply( v => ...someTransform.. return v.id);
ctx.export("idOutput", idOutput)

echoing-librarian-76448

10/06/2021, 2:56 PM

Sorry for the slow reply. I was able to get back to this today and ended up refactoring some functions to use

pulumi.StringInput

as a parameter instead of

String

I was able to avoid using

ApplyT

after making that switch. Thanks for the guidance on this

partypus 1

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