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

Unfortunately, I am definitely not a Network expert :see_no_evil:

Network is the worst resource provider in so many ways… And circular references being the top one.

okay, maybe you've come across circular dependencies before?

maybe i might resort to a post-Pulumi step to link the two then

This is the same issue I came across last week, there isn't a way to resolve this in Pulumi, or in ARM templates, the FD API is pretty bad. What I had to do was run a step after I deploy FD calling the Azure SDK to to link the rules engine to the route

I did this as part of the Pulumi code, but you could also do it externally

I don’t have a solution that doesn’t involve multiple updates with code changes in between

I would very much welcome
a) a blog post which provides a workaround (<@U014JNRGADD>?)
b) strong feedback to Microsoft about their API
c) suggestions for a potential solution for Pulumi in the future

I'd be happy to do a blog post, will try and do that this week. I know the new version of Front Door, with the CDN integrated which is in preview now is supposed to improve the deployment experience to hopefully this will resolve it

This is the new version - <https://docs.microsoft.com/en-us/azure/frontdoor/standard-premium/> not had time to look into it much yet

I read that a couple of days ago, but couldn't see much difference. Premium has better "threat intelliegence" which is opaque at best, but other than that their the same (but one is more expensive)

thanks for the help guys, saved me more time exploring things that aren't possible. I'll work around it with a 2-step process for now

Interesting, their example for that preview versions is using Microsoft.Cdn and no network/frontdoor <https://github.com/Azure/azure-quickstart-templates/tree/master/201-front-door-standard-premium-app-service-public>

The main difference is that it has broken out the FD components into separate top level items, such as "type": "Microsoft.Cdn/profiles/afdEndpoints/routes",

Seems they are under the CDN provider for some reason

<@U01MASTPJPR> note that standard and premium are both new, it's not just premium

ah, I thought standard was what we had already

That example is also using bicep, which is _so_ much easier to read

Those AFD resources are already in the provider if you want to give them a try <https://www.pulumi.com/docs/reference/pkg/azure-native/cdn/>

Damn I was about to hit this very same issue then, I thought its gonna be a breeze to put FD in front of our n clusters and let it do its job. 'subscribing' to this thread :C