Is it possible to delay the creation of Azure Key Vault Access Policies or to delay the creation of AppService Appsettings? Else I have a cyclic dependency. ("->" = depends on) AppService.AppSettings -> AKV Key AKV Key -> AKV AKV.AccessPolicies -> AppService.Identity

Have you seen the

dependsOn:

optional parameter?

No. The thing is that I can't add my AKV Key to the AppService Settings, because it is not defined yet. It has to be to defined later, because it depends the creation of the AKV. The creation of the AKV depends on AppService. Variable Scopes (ordered as defined in my C# Code): • AppService • KeyVault • Key I can' use they Key in AppService, because it does not exist so far.

I haven't played with creating/updating a AppService using pulumi. Are you saying that you cannot update the AppSettings in an existing AppService in pulumi? 1. Create AppService 2. Create AKV with desired Key and AppService.Identity (managed?) 3. Update AppService.AppSettings with Key Can you not do #3?

I am not aware of any update mechanism in Pulumi. @tall-librarian-49374 Do you know that?

You are not the first person to struggle with this… Unfortunately, Terraform modelled this wrong: app settings should likely be a separate resource. And we get this same model in Pulumi. Let’s try to work around this… Why does AKV depend on the App Service?

Thanks @tall-librarian-49374, that worked like a charm.