Thomas Kappler

Hi @Kmougari, apologies that we dropped this issue. Is it still relevant to you? If so, I'd need to know more about how you authenticate. The `tenantId` configuration you shared...

Thanks @Kmougari. Some more questions: 1. Did you create this role using the azure native provider? 2. Can you share the `Scope` of the role? It would be much easier...

I just spent a couple of hours looking into this under-documented API and I’m afraid it’s a size L task. I don’t think our existing "reset to default state" mechanism...

> RoleEligibilityScheduleRequests would be pretty simple, we’d only need to override DELETE and replace it with a PUT request. I take that back, since its PUT endpoint is only for...

In the line `gpu_instance_profile="None"`, the value is simply the string "None" because it's quoted. I'm surprised Azure didn't respond with a 400 here since `gpu_instance_profile` is an enum with defined...

I tried to repro but there's no auto-approvable quota for multi-GPU VM SKUs. *sigh* Submitted a support request. ```ts import * as resources from "@pulumi/azure-native/resources"; import * as containerservice from...

Hi @MatthewBettonMaif, thank you for the very detail bug report! I could easily reproduce it. I'll sync with the team on this issue.

In the provider's schema (schema.json line 393,495), the definition of `capabilities` is ```json "capabilities": { "type": "array", "items": { "type": "object", "$ref": "#/types/azure-native:documentdb:CapabilityResponse" }, "description": "List of Cosmos DB capabilities...

I just tried a few variations of this repro with the latest Azure Native 2.21.2 but always got the same result. Capabilities cannot be added nor removed with `PUT`. I...

/run-acceptance-tests