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

Please @mention me here that I get a notification for faster feedback.

&gt;  I’ve seen the `PolicyStatement` interface &amp; others <https://github.com/pulumi/pulumi-aws/pull/232/files?file-filters%5B%5D=.ts#diff-db03b6a8eac7dbf3938f52cfd3311a0aR31|are generated code>.
That particular interface is not generated currently - it is manually authored.    You can see that there is no "auto-generated" header on <https://github.com/pulumi/pulumi-aws/blob/27eaaaab8a4b431ec9dfe720f029189916b13dab/sdk/nodejs/iam/documents.ts>.

We are hoping to auto-generate it soon - mostly so that we can get the benefit of that strongly typed policy statement input in all languages - not just TypeScript.  This is tracked in <https://github.com/pulumi/pulumi-terraform-bridge/issues/132>.  Once that is done, these *would* be auto-generated.

More broadly - we are half way through moving all of the code-generation for SDKs over to a single unified schema-based code generator.  There is a single Pulumi schema for each package, that is used to represent all the pulumi resources, functions and types in the package, and that is used as the source for generating language-specific SDKs and docs.

You can see <https://github.com/pulumi/pulumi/blob/master/pkg/codegen/schema/schema.go> for raw details.  I expect we'll write up some more content on this schema once we get through the initial migration..

Oh, thanks for the quick &amp; thorough answer :+1:

I see. If there’s no
```// *** WARNING: this file was generated by the Pulumi Terraform Bridge (tfgen) Tool. ***
// *** Do not edit by hand unless you're certain you know what you are doing! ***```
header, we can assume that it is manually authored.

Yeah, I also wondered how do you (automatically) transfer changes in a PR from one language to another. So, it seems like you’re heading to sth. similar like <https://github.com/GoogleCloudPlatform/magic-modules|GCP's magic-modules>, right?

Yeah - there's some similarity to magic modules.  In practice our generator could one-day be another layer in front of magic-modules (we've talked to the team at Google about this).  In the same way - for our Terraform-based providers we currently lower them from the Terraform schema to the Pulumi schema and from there into individual Pulumi language SDKs.  For the GCP provider this ultimately looks like Magic Modules -&gt; Terraform Schema -&gt; Pulumi Schema -&gt; TypeScript.  We could imagine dropping the Terraform Schema step in there in the future and integrating directly into Magic Modules.