This message was deleted.

We already have quite a few enums already https://www.pulumi.com/blog/announcing-enum-support/

As Piers mentioned, enums are supported in the Pulumi schema, and we have added quite a few to the AWS schema already. Adding new ones is a trivial change, and contributions are welcome.

Oh that's great, I noticed that Enum members do not have their own docstrings. And I love that the class contains the link to the docs! (a year ago I did PoC parsing CloudFormation spec to yield a very similar result) Then I've looked at the

EnumValueSpec

and it looks like it can accept a Description and judging from the generated

CannedAcl

. Providing

EnumValueSpec.Description

will generate a docstring like this? Right? (while this docstring is valid and visible in PyCharm, VSCode ignores it 😞 ) I have an idea for how to contribute quite a bit of these Enums by pre-generating them from the API spec. But I'd need a hand setting up dev env, I developed only a very simple application in Go a while ago (on a different machine)

I noticed that Enum members do not have their own docstrings.

Fixed in https://github.com/pulumi/pulumi/pull/7374

Providing 

EnumValueSpec.Description

 will generate a docstring like this? Right?

Yes, once 7374 is piped through to the providers that will work.

But I’d need a hand setting up dev env

You’ll need to install go but other than that this should just involve adding the enums to

resources.go

and running

make build

at the root.