Thomas Kappler
Thomas Kappler
This is due to pulumi/pulumi#7735, point 4. As a codegen issue, it should be fixed in pulumi/pulumi. Marking as `upstream`.
Current status: the `MetricAlertActionArgs` vs `MetricAlertActionArray` is fixed. The `Criteria` issue is not.
Thank you @Zaid-Ajaj. I'm not sure I understand this correctly: > do we by any chance split the schema into sub-schemas when generating azure-native modules? [here](https://github.com/pulumi/pulumi-azure-native/blob/9115da997ffc9bf224859b34c5eb80a93d992aa7/provider/pkg/gen/examples.go#L70) we load the whole...
The test [is now failing](https://github.com/pulumi/pulumi-azure-native/actions/runs/10055800563/job/27804676959) with a different error: ``` - azure-native:dbforpostgresql:Configuration backslash_quote **deleting failed** error: Code="InternalServerError" Message="An unexpected error occured while processing the request. Tracking ID: 'f1645a3a-a6a4-4f9f-a580-42b0870eb3ab'" pulumi:pulumi:Stack postgres-p-it-runner-postgres-1e599fa5...
Debug logs show that the request to update the configuration is accepted (202) but then later returns `{"code":"OperationFailed","message":"{0}"}}`. ``` 3615: I0729 07:08:51.930664 96596 client.go:445] HTTP Request Begin GET https://management.azure.com/subscriptions/123/resourceGroups/rg61c1603c/providers/Microsoft.DBforPostgreSQL/flexibleServers/serverdf2d16b3/configurations/ssl?api-version=2022-12-01 ===================================================...
Just an update that as of Azure Native v2.24.0, this still reproduces (including Mikhail's unblocking suggestion).
> On February 29, 2024, continuous export will be deprecated as part of the classic Application Insights deprecation. [source](https://learn.microsoft.com/en-us/azure/azure-monitor/app/convert-classic-resource) So it's probably not worth investing into this particular resource. See...
Hi @Arttii, sorry you're running into trouble here. It seems as if `ARM_USE_OIDC: true` has no effect but I cannot see why. Two thoughts: 1. I'm not sure what purpose...
Nice! I think it's definitely worth pursuing since we have to do #1464 at some point. The question is, as always, prioritization, i.e., when to do it.
Hi @Kmougari! Can you share more about how authentication is configured in both providers? Note that Azure Native will _not_ re-use the configuration of Azure Classic, except certain environment variables....