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 behaviour here is a little strange - but is documented here: <https://www.pulumi.com/docs/reference/programming-model/#dynamic-resource-outputs>

ok, so I just need to define the interface and use type annotations?

Not quite (and I actually see those docs are slightly confusingly phrased).

The salient part are the `undefined`s in this:

```
 super(myprovider, name, { myStringOutput: undefined, myNumberOutput: unedfiend, ...props }, opts);
```

Any outputs you want to set on the resource object need to be passed as input properties (set to `undefined`) in the args bag.

<@UB3BGTV63> that works great, thanks a bunch!

yes, I will say those docs are a bit confusing since they show all the interface and type hints which most people using JavaScript won’t be using typically. The important bits (setting the undefined values in the ctor) got lost in the noise.

But it makes sense now!

Yep - definitely need to fix up that section.  Glad it's working though!