https://pulumi.com logo
#contribute
Title
# contribute
f

fast-sandwich-30809

09/01/2023, 2:02 PM
Morning all. I'm looking to understand the build process for the azure-native provider. There is a string[] that should be a string in the azure api spec, and this has halted our customer onboarding process. My options seem to be: 1. Downgrade to an old version of the azure-native provider, so that I can downgrade the api for the resource type in question 2. Manually patch the az-native provider - this seems hard 3. Make a PR against the azure spec - this seems to be the easiest option, I just want to make sure I do it in the right place
m

melodic-tomato-39005

09/01/2023, 2:08 PM
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?
f

fast-sandwich-30809

09/01/2023, 2:35 PM
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
Here's the next roadblock - since this is a "breaking change", it needs to be reviewed, which means sitting through the three-day review queue - but I can only get into that queue by removing the
ARMChangesRequested
label - and as a non-MS employee, I can't do that. I have no idea if anyone will ever look at it.
t

tall-librarian-49374

09/01/2023, 6:45 PM
Thank you for doing this work Ethan! I'll watch closely how they respond to your PR (I hope they won't ignore it!)
By the way is there a corresponding Pulumi issue open? Maybe we could think of a workaround for you?
f

fast-sandwich-30809

09/05/2023, 1:07 PM
There is! And I recognize your name 😉 https://github.com/pulumi/pulumi-azure-native/issues/2639
I had an idea over the weekend (it's probably not a good one) - I'll pitch it in #azure