@incalculable-sundown-82514 is there some way to derive from one of the pulumi classes so that I can have a new resource that has its inputs resolved and called as part of the dependency process so that I can access the outputs of other resources? The only way I can see currently is to define a custom resource that has its own provider and pass in the cloud provider (eg AWS) as an option for its children to use. Does that mean I have to write something like pulumi_random as a provider so that the engine will call the appropriate invocations at runtime?

So in the JavaScript world, we have this thing we call a “dynamic provider” which lets you do pretty much that - you write a JavaScript class that implements create, read, update, and delete by doing code actions and the Pulumi engine arranges for them to be called at the correct time.

yup, we need that sort of serialization to get user code to the other side of the engine 🙂. Where is the code that deals with the JS dynamic provider? I’ll have a look at how hard it would be to pythonize it 😄