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

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?

Circular dependency. For example, Zone depends on FrontDoor, while FrontDoor also depends on Zone Records.

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.