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.

Pulumi Community

You will most likely want to construct this client inside your CRUD implementations (or in a helper they call) using information passed in as arguments.   When the data arrives at your CRUD implementations it will be raw `strings`s, not `Input&lt;string&gt;`.

but a `constructor` in the `ResourceProvider` that deals with all the CRUD implementations, will mess with the arguments that’s receiving from what I’ve noticed. How do you suggest doing it? Any example I can have a look at?

<@UB39JFCKC> this is what I’ve been trying to do. <@UB3BGTV63> has give it some thought, but it’s something I had already looked, with no initial success

One thing to keep in mind that the provider code will run at a different time and in a different process than the resource code. Therefore, I'm not actually sure that you can pass clients between them.

I would stick to the recommended mode of <https://github.com/pulumi/examples/blob/master/azure-ts-dynamicresource/cdnCustomDomain.ts>

with two types of arguments (one with Outputs, other without) and passing them along

it was a very weird thing that I managed to resolve by clearing out a bit the state file… but definitely there was something in there cached