Instead of specifying all the possible backends in...
# general
e
Instead of specifying all the possible backends in the ctor of FrontDoor, is it possible to add the backends AFTER the frontdoor object has been created? see https://www.pulumi.com/registry/packages/azure-native/api-docs/network/frontdoor/#create-or-update-specific-front-door
w
I do not see a way to do that since backendpools are not available as a separate resource. Is there a problem you are trying to solve that is hampered by this?
e
Circular dependency. For example, Zone depends on FrontDoor, while FrontDoor also depends on Zone Records.
w
So, there’s this issue with some patterns/approaches: https://github.com/pulumi/pulumi/issues/3021#issuecomment-713270279 Otherwise, if possible, constructing the value that would be the
.id
(or whatever value) of the other resource for the initial resource declaration and using that instead of a
my_resource.id
(or whatever) implied reference can work.
e
Thanks. Gonna have a try.