Create FrontDoor with related ruleengines

[Norman-UL]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I would like to create a Front Door with some routing rules affected to rule engines. AFAIK :

• I need to provide the name of an existing FrontDoor while creating a RuleEngine
• I cannot create a RuleEngine while instaciating a FrontDoor
• I cannot link a rule engine to an existing RoutingRule
• I cannot create a RoutingRule outside the instanciation of FrontDoor

So I think Pulumi should implement a way to attach a rule engine to existing routing rule

Affected area/feature

• FrontDoor's RuleEngine
• RuleEngine

Thank for your help

[viveklak]

This seems to relate to https://github.com/pulumi/pulumi-azure-native/issues/1112

[danielrbradley]

Issue #1112 should now have been resolved by PR #2755 . The front door resource didn't appear in the list of affected resources, so I think this is a slightly different issue.

From the described problems, the issue is how the FrontDoor and its RoutingRules has been modelled by Azure as a single resource, but the RulesEngine is a separate resource. The RulesEngine depends on the FrontDoor, but the routing rules depend on the RulesEngine.

There are no endpoints in the specification to allow the modification of the routing rules separate to the frontdoor:

Azure have built a cyclic dependency into their resources which makes it impossible to use declaritively.

Here's an article on exploring the challenges around cyclic dependencies with a few listed workarounds including running the deployment twice on the inital deploy to change the desired state of the FrontDoor on the second deployment.

[danielrbradley]

This is blocked on implementation of:

• https://github.com/pulumi/pulumi/issues/13999