This message was deleted.

sparse-intern-71089

04/21/2023, 10:57 PM

This message was deleted.

dry-pilot-49577

04/21/2023, 10:59 PM

Context: The terraform provider (and pulumi registry item) for MongoDB don't include the Atlas DataAPI application service and dependents, so I'm building that as a set of dynamic resources. Code, Config, and Logs: https://gist.github.com/jakobo/bda66c77da6f9bfd4c0cdd50392f9ce4

green-stone-37839

04/21/2023, 11:01 PM

There is a known issue with accessing

pulumi.Config

inside dynamic providers. https://github.com/pulumi/pulumi/issues/4512

green-stone-37839

04/21/2023, 11:01 PM

My suggestion (same as issue comments) is to pass those needed values as args.

green-stone-37839

04/21/2023, 11:02 PM

Not saying that's your only issue, but likely one of them.

dry-pilot-49577

04/21/2023, 11:05 PM

I can definitely work around that one. Was following a pulumi video. Makes sense that wouldn't serialize well. Will report back. The current pulumi error is below which I'm just stumped on. (edit: code config and logs moved to <https://gist.github.com/jakobo/bda66c77da6f9bfd4c0cdd50392f9ce4>)

dry-pilot-49577

04/21/2023, 11:17 PM

Code and error updated to reflect current status. No change in the output. It's definitely at the library level, but if I can't use node-fetch, axios, got, ky, and others I feel rather stuck. Purrl gets around this by making the http calls in Go, but it's very difficult to marshal the bearer token (via

response.apply

through all the resources)

green-stone-37839

04/21/2023, 11:18 PM

😕 it's an odd error message. I can't take a look at the code further right now, but there should be no issue using

axios

or whatever HTTP client you want with a dynamic provider. Thats the whole point!

dry-pilot-49577

04/21/2023, 11:27 PM

That's what I thought too 😆 I suppose the following questions come to mind that might unblock me • What runtime is the serializer using at execution? My pulumi code is all ts with ES2020+node16 module resolution. It might be getting serialized for node16, and then executing in a different runtime • Is pulumi's ts-node config somewhere? Searching the repo turned up a lot of hits. I'm running

esm: true

& coupled with the compile targets I might be messing up the internal serialization

billowy-army-68599

04/22/2023, 12:09 AM

I would recommend opening a GitHub issue for things in the engine like this if you can summarise it

dry-pilot-49577

04/22/2023, 12:11 AM

I'll try. sweaty blob I'm still trying to wrap my own head around what I'm seeing. I will clean up this thread and move everything into a gist so it's easier to read. I've just got massive gaps in my understanding of how serializing works and why node 18/esm would cause it to fail out before even reaching preview.

dry-pilot-49577

04/22/2023, 4:43 AM

Traced it to the following GitHub issue, about 1.5 years old. https://github.com/pulumi/pulumi/issues/5294 They're likely to be the same root cause, as dynamic resources make use of the same serialization. It's just really easy to trip on native code. 😞

2 Views

Open in Slack

Previous Next

Pulumi Community

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.