Static Site Linked Backend creation fails with HTTP 500 error when not specifiying the region

[TechWatching]

What happened?

If I don't specifiy the region of the static site linked backend, the program fails with an Internal Server Error.
The Region property should be mandatory (at least when used with an App Service backend).

Pulumi does not automatically fill the region with the default Azure location, probably because it's called Region and not Location, or maybe because it should be filled with the App Service location.

Another problem is that when this error occurs, Pulumi execution sometimes does not stop and wait forever (I think until it timeouts) to says the update fail. It should fail fast.

Example

var staticSiteLinkedBackend = new Pulumi.AzureNative.Web.V20240401.StaticSiteLinkedBackend("stapp-test-dev-an-e352ae82", new()
{
    BackendResourceId= "/subscriptions/****-*****-****/resourceGroups/rg-test-dev/providers/Microsoft.Web/sites/wapp-test-dev",
    LinkedBackendName = "wapp-test-dev",
    Name = "stapp-test-dev",
    ResourceGroupName = "rg-test-dev",
});

In this example,

• wapp-test-dev is an existing App Service
• stapp-test-dev is an existing Static Web App (Standard SKU)
• rg-test-dev is an existing resource group

Output of pulumi about

CLI
Version 3.142.0
Go Version go1.23.3
Go Compiler gc

Plugins
KIND NAME VERSION
resource azure-native 2.74.0
language dotnet unknown

Host
OS Microsoft Windows 11 Pro
Version 10.0.22631 Build 22631
Arch x86_64

Dependencies:
NAME VERSION
Pulumi 3.71.0
Pulumi.AzureNative 2.74.0

Additional context

I think we should discuss whether or not we want Pulumi to automatically set this property with the Azure default location, which does not have to be the same as the backend location. In any case, documentation should be more helpful, logs as well, and also samples. And we should not wait for Pulumi to timeout .

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[pulumi-bot]

This issue has been addressed in PR #3759 and shipped in release v2.77.0.