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

yeah, I think table management isn’t implemented in ARM

too bad :confused: guess the only way around this is by creating the tables and ingest manual?

You could try to create them with Azure SDK from your Pulumi program

I'm not certain that I understand what you mean

do you mean with a callback on the namespace, and then calling an external program?

with the external program being a nodejs app that uses the sdk ?

You can install the Azure SDK to the same program and call it directly

true :slightly_smiling_face: that might work; what would be the prefered way to trigger the azure sdk script in such a way that it runs after the cluster and hubs are made, but before pulumi tries to make the evenhubconnection ?

Then it’s best to make a dynamic provider

that sounds rather complex for my problem :confused: do you know whether there's somewhere an example of this kind of pattern?

It’s not that complex… Here is an example: <https://github.com/pulumi/examples/blob/e990699e03ff31af95bd62b08f31f8fb99b11ccb/azure-ts-static-website/staticWebsite.ts>

You could call the Azure SDK from an `apply` callback but then it would be called on every `pulumi up`. A dynamic provider integrates nicely into the resource lifecycle and CLI.

cool, thnx! I'll try to get it working tomorrow :slightly_smiling_face: