This message was deleted.

Are you saying that when you try to access, say,

new_account.sid

, it throws an error or something?

Yes

Can you share the error message?

Yes. When I access it just with

new_account.sid

everything works fine but when I pass that into another resource I get the following:

TypeError: 'Output' object is not callable
 error: an unhandled error occurred: Program exited with non-zero exit code: 1

Are you familiar with the

apply

stuff in Pulumit: https://www.pulumi.com/docs/intro/concepts/inputs-outputs/

I've been taking a look at it. I tried using it and got the same error though

I’m not sure what’s happening. FWIW, I hacked out a python dynamic resource example (https://github.com/MitchellGerdisch/pulumi_work/tree/main/py-dynamic-resource) that uses an output from the dynamic resource (acl) as an input to creating another resource (S3 bucket) and it works as expected. I’m wondering if the output from the API call you are making and returning is not as expected?

That can't be it because my server has no incoming requests.

I’m referring to the create in the dynamic resource:

def create(self, props):
        subaccount = self.parent_client.api.accounts.create(friendly_name="{}-{}".format(props["name"], stack))

Are you sure

subaccount

and more importantly

subaccount.sid

is defined? or that

new_account.sid

is defined in the calling code?

I know that all of the subaccount stuff is defined, and when I check the stack export everything exists as it should

Meaning you have a

pulumi.export("new_account", new_account)

after the

new_account

declaration, and see that new_account has the various properties?

I don't, I believe it does that automatically? when I run

pulumi stack export

I everything outputs like it should

That should be a valid representation of things. But I would suggest throwing that

pulumi.export

in your code and see what it shows - just to see what outputs the code sees.

Ok, I'll give that a try

And the error is due to this line, right?

<http://requests.post|requests.post>("<http://localhost:5000>", {"f":new_account.sid.apply(lambda sid: f"{sid}")}),

Interesting, I'll test that

Good - sorry I didn’t pick up on that line earlier in the thread.

No problem!