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

Hi <@UTM78AL94>, there are a couple ways to address this. One way is to add definite assignment assertions to each property. <https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-7.html#definite-assignment-assertions>

Adding an exclamation point after the property names like:

```    public readonly endpoint!: pulumi.Output&lt;string&gt;
    public readonly token!: pulumi.Output&lt;string&gt;
    public readonly description!: pulumi.Output&lt;string&gt;```

Another way would be to set `strictPropertyInitialization` to `false` in `tsconfig.json` .

We need to update our example in the documentation. It was written before more recent versions of TypeScript got stricter about this by default.