Thomas Kappler

/run-acceptance-tests

Likely the same root cause as pulumi/pulumi-metabase#3.

Since there seems to be a working solution, I'll close this issue, but please feel free to re-open if necessary.

Hi @Werner-Swart-83, thank you for the detailed report and for your offer to help. Unfortunately, this endpoint isn't trivial to add. Pulumi operates on a resource-based model, whereas this endpoint...

Thank you for reporting this, @holtsoftware. I can reproduce with this complete program: ```csharp using Pulumi.AzureNative.AppConfiguration; using Pulumi.AzureNative.AppConfiguration.Inputs; using Pulumi.AzureNative.Resources; using System.Collections.Generic; return await Pulumi.Deployment.RunAsync(() => { var resourceGroup =...

It's the `/` in the key-value name that trips up the Azure endpoint and makes it respond, confusingly, with 404. The exact same program just with the slash removed works...

We're probably not doing the right thing in az-native when generating the dbforpostgresql schema. `providers/Microsoft.DBforPostgreSQL` has distinct services in it, with similar resources under different paths, e.g., [Firewall](https://learn.microsoft.com/en-us/rest/api/postgresql/flexibleserver/firewall-rules/create-or-update?tabs=HTTP) at Microsoft.DBforPostgreSQL/flexibleServers/...

Thank you for your contribution, @mothran, and apologies for the late response. Looks like this PR was made obsolete by other changes in the meantime, removing the reference to `dbName`...

Hi @sebastianbertoli , thank you for your contribution, and sorry for the delay in responding! It just so happened that the latest upgrade to this provider, #2215 less than a...

/run-acceptance-tests