Hi everyone, does anyone know if the azure-native provider automatically adjust key format from camel case before making a request against the Azure API? For example, the azure-native v3 ManagedCluster has a key mis-match for its autoScalerProfile setting. Pulumi Azure native provider use camelCase. The Azure spec is expecting kebab-case. At the moment, latest azure-native v3.8.0 is throwing the following error when any of the key under autoScalerProfile are defined:

Invalid request body. Converting request body to a managed cluster encountered error: json: unknown field \"scaleDownUtilizationThreshold\" Check that the field is in the right location, is spelled correctly, and is supported in the API version. Visit aka.ms/aks/apiversions for more API version information..

Azure is expecting

scale-down-utilization-threshold

instead of

scaleDownUtilizationThreshold

. Let me know if you think it's a bug, I will create a ticket in GitHub.

Thanks for cutting the issue, I think another person noticed this last week too. Let me take a look and get this prioritized

Hi @blue-jelly-20468, I created the following draft PR but it feels a bit hack: https://github.com/pulumi/pulumi-azure-native/pull/4391 It does work though 😛 If you can have someone pointing me how things should be done then I can spent more time on it