It seems that

config.require

doesn't work so well in a dynamic provider async

create

function.

I'm not sure exactly why you see that error - but in general it likely makes sense to get the values of these configuration settings outside of the

create

callback, and then capture the value of the config setting. See the note at the end of https://www.pulumi.com/docs/reference/programming-model/#dynamicproviders for details on the unusual execution model for Dynamic Providers that leads to this kind of requirement.

ok got it — i've read that note but tbh i've had trouble fully understanding it capturing the config value outside of the callback does work. Thanks Luke!