Hi all. I have put together an initial version of a component resource for installing Twingate connectors into GCP. It seems to be working for basic usage. It is here: https://github.com/activatedio/pulumi-google-twingate What are some recommended practices for handling namespaces and project names? This is a component provided by my company, so the NPM organization is “activatedio”, as is the GitHub, Given it is a pulumi component for installing Twingate on GCP, the npm module can be “@activatedio/pulumi-gcp-twingate”. Go is straightforward with the git path. What are the recommendations for .Net and Python?

@millions-account-72180 Python/Pypi has no concept of namespaces, so you have to resort to this: https://github.com/jaxxstorm/pulumi-aws-securebaseline/blob/main/schema.json#L144 .NET does have namespaces, i'm not sure we support them yet. cc @broad-dog-22463 - is there a way in the component schema to namespace packages?

Yes we do - RootnameSpace is a param in the Csharp section

I set RootNamespace in my schema and now my

make build

gives me the following:

/home/btomasini/git/activatedio/pulumi/pulumi-google-twingate/sdk/dotnet/GoogleTwingate/Connector/Inputs/TwingateConnectorArgs.cs(17,56): error CS0234: The type or namespace name 'ResourceArgs' does not exist in the namespace 'Activatedio.Pulumi' (are you missing an assembly reference?) [/home/btomasini/git/activatedio/pulumi/pulumi-google-twingate/sdk/dotnet/Activatedio.Pulumi.GoogleTwingate.csproj]

What version of Pulumi-terraform-bridge are you using?

I am basing my project on this: https://github.com/pulumi/pulumi-component-provider-ts-boilerplate

Ah it's a conponent :/ there may be a bug there then

Yea please that would help! If you are interested - would you be interested in sharing an experience repo on the problems you faced? I can share my email address

Of course. Would be more than happy, and could do a quick 5 minute working session if that would help.

In the ts boilerplate repo will be awesome :)