Are there already good examples / practices around creating reusable python modules for pulumi? In terraform I make my customers almost always write terraform modules so that other teams can just "import" them into their code. In nodejs I would create a custom component that I

require

into my

index.js

. Does the same work with python programs so I can just

import

them into

__main__.py

?

yeah, why not. its just python code

@colossal-room-15708 Yes - absolutely. Ultimately our own SDKs are just python packages.

I’ve updated my

pulumi-aws-vpc

library to have python support, but haven’t quite finished yet:

That’s probably the most complete example I know of for this right now. I’m planning to expand some of the examples around this kind of pattern soon. If you have specific questions etc that would be useful to guide this!

Yes, cool, I'll work on a few things today to see if I can get this working as well. 👍

So, looking at your example @stocky-spoon-28903, I don't need to create a custom component as described here? https://pulumi.io/reference/programming-model/#components

scratch that, GitHub search didn't show me this one here: https://github.com/jen20/pulumi-aws-vpc/blob/jen20/version-2/python/jen20_pulumi_aws_vpc/vpc.py That's a good example, thanks.

Why does this here work in one case, but not in the other?

parameters={
                                                   "bastionHostName": "%s-bastion" % (location),
                                                   "publicIpAddressName": self.pip.name,
                                                   "location": location,
                                                   "bastionServicesVnetName": vnet_name,
                                                   "bastionServicesSubnetName": self.subnet.name
                                               }

location

in both cases is an input param to the component, which is an output from a resource outside of this component

I guess I'll have to use

.apply()

, but to me, not being super deep into python, it seems strange that it works in one, but not the other.

"bastionHostName": location.apply(lambda location: location + "-bastion"),

fixed it

what python concept am I missing here?

when will awsx for python be available?

Are there any aws lambda examples that are a little more than hello world? What if your lambda function has dependencies? Currently we have a pipeline that builds deployable versioned artifacts that can be deployed with cloudformation. The pipeline handles doing pip installs for any dependencies.

in our pipeline i use a docker container to load on top of the code, runs a pip install inside a venv mapped to the local filesystem, then it zips it all up and uses pulumi to deploy the zip

i have some examples i could share if you’d like, send me a msg

why? i just have a container with all the prereqs

is there any documentation describing how pulumi expects the users to handle coroutines and when they're ok to use?

like, for example, can i have a

ComponentResource

spawn its sub-resources in a

Task

?

(this is coming up for me a lot because

route53.get_zone()

returns an awaitable, not an

Output

, so i'm having to write a bunch of utility stuff to manage the async flow while still keeping the structural definitions syncronous)

I can assume that the answer above about awsx also applies to cloudfx?

ok, just for kicks, i tried doing the initialization of a

ComponentResource

in a coroutine wrapped in a

Task

and pulumi just hung

Hello ! I'm looking at Dynamic Providers in Pulumi (https://pulumi.io/reference/programming-model/#dynamicproviders) and I see that Python isn't yet supported for this feature. Is there any ETA for that ?

Anyone else having trouble with

FileArchive

? I can't give it a zip (created by 7-zip) or a directory

and

AssetArchive

says "expected an archive, but source is not an archive"

oh, that might just be a

BucketObject

thing?

given an

ResourceOptions

or

Resource

, can I get the provider that would be used? I want to get the current aws region for a given component resource