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

The reason why I need this is because we use pulumi to pass variables to Nomad and unfortunately `&lt;pulumi.output.Output object at 0x7d5389558400&gt;` is not a str and we get runtime type errors during pulumi preview.

The potential workarounds are
1. skip pulumi preview, and forget about the safety guarantees
2. Write a hcl2 parser and use reflection to mock out the actual types during pulumi preview
3. Split the pulumi projects and chain them. This requires making changes into a 2 PR process

<@U02G0S85R0C> you need to it inside an apply 

<https://leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html|https://leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html>

From <https://www.pulumi.com/docs/intro/concepts/inputs-outputs/>
```During some program executions, apply doesn't run. For example, it won't run during a preview, when resource output values may be unknown. Therefore, you should avoid side-effects within the callbacks. For this reason, you should not allocate new resources inside of your callbacks either, as it could lead to pulumi preview being wrong.```
Unless something has changed, apply doesn't run during pulumi preview, so its not applicable

Sorry, I was focusing more on your need to interpolate the type T, not the preview par. You can't get the raw type T outside an apply 

Ok, thank you. I thought it was a long shot.

It's definitely possible to do what you're trying to do though, if you could explain why the ultimate goal is I can help with that 