This message was deleted.

Hi Ethan. Option 3 is generally the best, but you’re at the mercy of the Azure team to respond and fix it. The right place would be https://github.com/Azure/azure-rest-api-specs/issues. Does the issue occur in all Azure API versions? Your option (1) suggests probably not, otherwise downgrading on the Pulumi side wouldn’t help you. Can you import an older API version while using the current az-native?

Hey Thomas! I've been feeling that - the issue has already slid to page 3, with no human response other than a "cxp-attention" tag. https://github.com/Azure/azure-rest-api-specs/issues/25202 The most recent Azure API version that does not include the problematic field is 2021-11-01. Pulumi azure-native exposes this version (and older!) but only for select few resources.

ls v2020*

and

ls v2021*

show

virtualMachineScaleSetExtension

, but no

virtualMachineScaleSet

. It looks like the oldest version exposed is from 2023. I would have to downgrade to azure-native v1 to get the 2021 api. The issue in question is extremely simple, and while the Azure team has 1.3k issues, they do seem to close (some) PRs - and I'm pretty sure I've even narrowed the issue down to the line. https://github.com/Azure/azure-rest-api-specs/blob/80c21c17b4a7aa57f637ee594f7cfd6[…]Compute/ComputeRP/stable/2023-07-01/virtualMachineScaleSet.json They've wrapped some of the field keys in an

items

block, which causes downstream consumers to mis-interpret the field as an array

Thank you for doing this work Ethan! I'll watch closely how they respond to your PR (I hope they won't ignore it!)

There is! And I recognize your name 😉 https://github.com/pulumi/pulumi-azure-native/issues/2639