set the channel description: Need help contributing to Pulumi? Have a question about how the code works? This is the place you want to be!

@bitter-oil-46081 Hey! I'm interested in maybe helping out for .NET 🙂

Hi @flaky-continent-74538! Glad you found the slack channel and sorry for the bad link earlier. I just pushed a few more commits, I'm still trying to get a sense for everything (which will require probably another day or two of exploration before I really have a well formed plan of attack) but in the meantime It would be interesting to just a sense of the sort of code you'd like to write in C#. Put another, what does your ideal Pulumi program in C# look like? I built the prototype of c-sharp interactive (mainly to learn that as well) but I don't think it's the right long term direction.

The team is going out to drinks shortly to celebrate the launch, but my plan for tonight is to read and think a lot.

Sure! Are you interested in designing the high-level "cloud" version, or the tfgen version for now?

Personally, I'd love to see Pulumi integrate with ASP.NET Core in an almost invisible way

Maybe have the resources defined in dependency injection?

Oh, something I'd like: shared resources between apps, each with their own access levels. For example, say my "photo processing" service has a queue. Other services should be able to access that queue to enqueue things. I think we'd need the concept of resource ownership

Not sure about C# code, but I can imagine really nice Pulumi code with F# computation expressions

.NET would probably be used a) to reuse existing domain code, e.g. create a queue + processor for each implementation of an interface in codebase b) to combine code and infra for things like Azure Functions

So Haskell? [by the community] :)

The way the language provider and engine communicate is via gRPC, so you'll need some way to crack that nut (https://github.com/grpc/grpc-haskell looks like it could have been a thing but the

README

says it is experimental and it looks like there have been no commits in 9 months). Another option would be to have some external bridge that translates gRPC into some wire format that makes more sense there. When I was starting the dotnet language provider my plan of attack was first to just get the language plugin launching and have it print hello world. Pulumi will display things written to stdout as info messages during a deployment. The next thing was to start using the gRPC interface to send logging messages from the language host back to the engine. Once you have that, you can actually start on the "hard work".

Which is the best repo for opening issues around CLI usability? Just noticed the colours seem interact in an unexpected way given some terminal colour schemes

@stocky-spoon-28903 uploaded a file:

@stocky-spoon-28903 pulumi/pulumi! https://github.com/pulumi/pulumi

this is the repo that builds the CLI

https://github.com/pulumi/pulumi/issues/1486 is somewhat related.

I’ve opened https://github.com/pulumi/pulumi/issues/1550 to track it and linked that back to #1486.

@bitter-oil-46081 could we possibly connect to flesh out more of the .NET details this week, perhaps on either Wednesday or Friday? I posted on issue #1526 to inquire about some of the things you suggested, such as closure serialization. I just want to build a more complete understanding of what you put in the issue to be sure I'm not making false assumptions.

So I think I have a good start on an OpenStack provider. Was mostly a pretty simple copy of the aws/azure providers but had one annoying complexity. The terraform-openstack-provider uses loads of different revisions of gophercloud, and dep doesn't support different revisions in one project. I put together https://github.com/Frassle/terraform-provider-openstack/tree/pulumi-master quickly to just get all gophercloud revisions to the same sha. Could then depend on that repo in the pulumi-openstack provider (https://github.com/Frassle/pulumi-openstack), and I've then managed to build that and use the nodejs module in a little pulumi project to create a compute instance on a public openstack cloud.

That’s excellent! @big-piano-35669 @white-balloon-205 @bitter-oil-46081, any ideas on next steps?

@helpful-vegetable-35581 Just took a quick pass, and this looks great! If you have a simple example, would be great to add that to the repo as well (following a similar pattern to what `pulumi-aws`/`pulumi-azure` do). I'm going to see if I can get ahold of an OpenStack instance to try this out myself.

Is there a guide to licensing etc for adding overlays to the AWS library?

I didn’t spot a CLA etc, but all files seem to have a Pulumi copyright on them

We elected not to use a CLA or DCO, to ease contributing. Everything is Apache 2.0 licensed. A bit more info is available here https://github.com/pulumi/pulumi-aws/blob/master/COPYRIGHT, but it's (we hope) pretty standard stuff.

@big-piano-35669 so for new files, do you expect the copyright to have pulumi copyright or contributor copyright on them?

I’ve opened https://github.com/pulumi/pulumi-aws/pull/251 to try the CI, not anticipating it will build yet necessarily!

Hello, Is there a way to use AWS profiles with switchrole and no keys defined ?

Re Openstack support. I've raised an issue on the terraform-openstack provider to get their vendor dependencies straightened out (https://github.com/terraform-providers/terraform-provider-openstack/pull/359) they approve of the change but need to fix some breaking issues and ensure stability before merging it. Once that's in pulumi-openstack can depend directly on the official terraform provider. Has there been any further thought about pulling in the OpenStack provider as an official repo? Even if it's just advertised as alpha quality it would help giving it a stable package name.

Has there been any further thought about pulling in the OpenStack provider as an official repo?

Yes - we'd love to do this! I can work with you on details of that.