Anyone have any luck configuring with azure native front door? I am trying to connect with private endpoint and call web app but wow is it hard to find a sample and the combinations of settings are a bit crazy

IMO, this is Pulumi's biggest weakness. Their scope is so ambitious that the basics that are needed to truly use everything that's available are left behind, e.g. documentation and meaningful samples. What I've generally done to try to figure this kind of thing out is: a) manually create the resource you want in the Azure portal, e.g. in a "poc" resource group b) use "pulumi import" against that "poc" resource into a dummy stack to generate the pulumi code needed to create the desired resource c) use the generated code as a template / sample and adjust accordingly

Really you can import arm?

I've imported a lot of Azure resources, specifically to see what the generated code looks like. The trickiest thing is usually figuring out the correct full resource ID (pseudo-URL) of the resource you want to import.

I will say looking at my arm template is giving me some light bulbs. Fingers crossed. Thx for the tip though

That's the other thing I've done a lot - export the arm template and try to deduce property names and values for the Pulumi objects.

It doesn’t help that routes are combined with the front door resource when they are separate otherwise

I haven't had to use front door for anything to this point. My "back of napkin" mental plan for the occasion when I think I need it is to use CloudFlare instead and move anything that reasonably can be hosted on CloudFlare to CloudFlare workers.

This is a poc for work I am trying to show teams there are better options than terraform. I don’t blame Pulumi per say it’s the APIs they build from but pain is pain

Pulumi auto-generates all this stuff from the provider (e.g. Azure) APIs. At a minimum it would be useful for the Pulumi docs to have links to the provider docs.

Something for sure

Maybe not quite related, but a hint: For huge resources like Frontdoor, a lot of folks miss that you can use relative IDs to define links between its different parts, e.g.

$self/frontEndConfigurations/my-frontend

will expand

$self

to the Frontdoor ID, so you don't need to hard-code it yourself.

Turns out the problem is front door falls under cdn and network namespace. And guess what chatgpt thinks you asked for front door here is front door classic

oof...