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

Unfortunately this is a part where our Python docs aren’t sufficient - `routes` has to be a list of dictionaries with a set of keys instead of a string:

<https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/ec2/#RouteTableArgs-routes>

Python snake_cases the properties instead of camelCase like Node, but these keys are the same.

Thanks for the help! I’ll give it a shot. Do you guys take pull requests to the reference documentation? I got the sense it was cobbled together from different sources.

unfortunately, it’s autogenerated. We basically have to improve the code generator in pulumi/pulumi-terraform to be better - I’ve been landing a number of fixes that will improve docs, but there’s always more that can be done :stuck_out_tongue:

the hardest thing here re: Python is that Python, being totally untyped, doesn’t have a great built-in way to document the shape of dictionary objects that get passed as inputs to resources. Boto rolled their own documentation generator to do this

It’s much easier with TypeScript because TypeScript has an actual interface type corresponding to the e.g. `RouteTableArgs` type that encodes the things you can pass to it

Yeah, I saw some type hints in some of the code, but in general it hasn’t seemed to have really had much of an impact (more broadly, not just this project).

I might learn TypeScript mostly, well, for the type support.

Yeah, it’s true that TypeScript has a pretty incredible experience re: types.

I’m trying to see what I can do re: Python and IDEs, but unfortunately it looks like there’s not a comparable experience for Python programs.