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 guess I don’t quite understand the issue. What’s the problem with creating the subscription after the Azure Function?

Thanks for the reply <@UB39JFCKC> :slightly_smiling_face: The problem is that we need to deploy the Azure Function binaries as well as the application resource, before creating the subscription. The way we've modelled this so far (and implemented in our pipelines) is as two quite separate processes, with separate pipelines: one for our Pulumified infrastructure (deploying an empty shell), and one for our application deployment into that shell.

I'm happy to accept that this separated approach is wrong, if that's the case. I guess I'm looking for some direction on good practices around placing Pulumi in our pipelines as much as to solve the issue. If the split we have is not good practice then of course we can fix it by combining the deployment pipelines; if it is accepted practice, then we need to find a way around this issue.

Thinking about again, even with a single pipeline we'd still have to run our Pulumi project twice, unless that project _also_ downloaded and deployed the Function zip package

More research indicates this is a problem with Event Grid itself — the same two-phase deployment is required for ARM deployments also :disappointed: