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

Can you give the specific example, maybe with code?

I create an array of RecordSet (Azure) dns records like

like `const recordSets = [].map(new RecordSet)`

and then I use this array inside FrontDoor, as dependsOn

what happens, frontDoor starts it’s update earlier and I get failure from pulumi engine

```      ' ~  azure-native:network/v20200501:FrontDoor frontDoor **updating failed** [diff: ]; error: autorest/azure: Service returned an error. Status=&lt;nil&gt; Code="Conflict" Message="Cannot delete frontend endpoint \\"fd6test.astrumu.dev\\" because it is still directly or indirectly (using \\"afdverify\\" prefix) CNAMEd to front door \\"<http://emtkdev.azurefd.net|emtkdev.azurefd.net>\\". Please remove the DNS CNAME records and try again."\n' +```

You're creating an array, then depending on the array being created? The array finishes being created immediately, it won't be dependent on the resources within the array.

uh, oh… I think I know what’s wrong :slightly_smiling_face:

Ah, you're setting that as the entire array. Ok.

I think the problem, that I delete single RecordSet from array that I expect to be dependedOn

so it’s deleted in runtime, but it’s not there anymore :slightly_smiling_face:

so frontdoor update triggers earlier then expected

Thanks for the heads-up, I'll stick with AWS :slightly_smiling_face:

looks like pulumi has it’s cleanup process at the end of the runtime

which means, dependsOn will not wait if I deleted that resource in my array and trigger update asap

and then only do the delete… which I can’t do