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.

Pulumi Community

In general you should avoid creating resources and exports in apply

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`

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

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.

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

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:

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

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