Daniel Bradley

@justinmchase agreed, we'll leave this open for visibility. If anyone who's experienced this can let us know if it's been fixed upstream, we'll then close this to clear the issue...

Hi @ArtunSubasiStihl thanks for reaching out. I'm not very familiar with this particual integration. The Azure Native documentation link you sent looks like the right setting - [`SecurityProfile`](https://www.pulumi.com/registry/packages/azure-native/api-docs/containerservice/managedcluster/#securityprofile_csharp)`.`[`AzureKeyVaultKms`](https://www.pulumi.com/registry/packages/azure-native/api-docs/containerservice/managedcluster/#azurekeyvaultkms_csharp) looks equivilent...

@vdboots I've just re-created and run your example given above, filling in the missing resources: ```csharp using Pulumi; using Pulumi.AzureNative.Resources; using System.Collections.Generic; using Pulumi.AzureNative.ApiManagement; using Pulumi.AzureNative.ApiManagement.Inputs; return await Pulumi.Deployment.RunAsync(() =>...

@mikhailshilkov Yes, my change was applied in the Azure portal ... I added the following rules to the `` section: ```xml ```  What's the change you're actually applying to...

Here's the diff between the bad -> good dashboard examples provided: ```diff diff bad_dashboard.json good_dashboard.json 5,6c5,6 < "dashboards_dash0b8aeffa_name": { < "defaultValue": "dash0b8aeffa", --- > "dashboards_dash84b4f108_name": { > "defaultValue": "dash84b4f108", 15c15...

It seems that we've managed to reduce the number of incorrectly formated examples, but quite a few remain. It's possible to identify the affected resources by searching for a newline...

The cause of the missing formatting appears to be related to the code being invalid and therefore failing when we attempt to reformat it. One example of this is `azurestackhci/UpdateRun`....

I'm currently attempting to recreate this myself but it's taking some time (> 20 mins). The `Id` property of the `api` is the internal identifier of the resource (the full...

On your second question: > 2. According to the Azure SDK Rest API specification found [here](https://learn.microsoft.com/en-us/rest/api/apimanagement/previous-ga/api-release/create-or-update?tabs=HTTP). Both the name and id are required. Name goes in the route and id...

I've confirmed that using the API `name` output property resolves this issue. I also recreated this in TypeScript to ensure the language wasn't a factor: ```typescript const resourceGroup = new...