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

Can you give an example of the error and what you are trying to do? It'll be a lot easier to point you in the right direction that way.

You should be able to pass in the Output to another resource's Input directly. If you need to put strings together or create json you'll need to use `apply`. It's possible the errors you are running into is when you try to `print` the output?

i’d have to do a bunch of re-rework to get it producing the errors again, we’d just refit everything to use an apply callback any time an output is used

then i noticed our previews were short, and _then_ i noticed the note in the docs

&gt; we’d just refit everything to use an apply callback any time an output is used
that's probably not necessary TBH

i was hoping so, but we’ve not gotten it fully working without that

i’ll keep trying for now and post again if i get the errors back, thanks for looking

Are you creating the resources inside the apply?

Also, perhaps this blog post is helpful: <https://www.leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html>

Yeah currently all the resources that depend on the value of any output are being created in an apply

(which was to avoid errors relating to outputs, still don’t have those back)

FWIW, you should just be able to do this:
```res1 = MyResource("my_resource", property="blah")

res2 = OtherResource("foo", dependent_property=res1.property)```
If you need to transform the output (like add something to the string)
```res1 = MyResource("my_resource", property="blah")

res2 = OtherResource("foo", dependent_property=res1.property.apply(lambda x: f"new-string-{x}")```

The reason that your previews are inaccurate are 100% because you are creating those resources within an apply. There are <https://pulumi-community.slack.com/archives/C01PF3E1B8V/p1638417874251200?thread_ts=1638412674.250500&amp;cid=C01PF3E1B8V|some instances> where it is unavoidable, but for the most part you should be able to do it without creating resources in the apply.

yeah i knew it was the cause of the wrong previews, thanks for the datapoint though

i think i’ve got this sorted out, tldr your `print` suggestion was not far off, Outputs were just being used as an argument to not-a-Resource