-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azure-mgmt-compute: VirtualMachineIdentityUserAssignedIdentitiesValue became mangled somewhere between 13.0.0 and 17.0.0 #14150
Comments
Thanks @jazelenk for reporting this, @nickzhums could you take a look at this |
@jazelenk there was a major version upgrade in Python SDK from 13.0.0 to17.0.0. This is actually the reason why there was such a big version jump and an indication for important new changes (and breaking changes) The new version of Python SDK introduces some breaking changes but also important new features such as unified authentication, distributed tracing, and much more. You can find a detailed quickstart and migration guide on this page. link Do you guys regularly upgrade python ask as a routine? |
Yes, I understand that the new version contains a lot of breaking changes. This change seems unnecessarily breaking, however, and TBH, it just looks wrong, like autorest blew a gasket or something. |
Hi @jazelenk , We are investigating on this and find this is related to a naming-convention change in codegen. I will have a PR in swagger repo for this so that it can be fixed in next azure-mgmt-compute release. |
@msyyc do you know if this is fixed? |
Hi @jazelenk. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
Hi @jazelenk, since you haven’t asked that we “ |
Describe the bug
azure.mgmt.compute.models.VirtualMachineIdentityUserAssignedIdentitiesValue
has changed toazure.mgmt.compute.models.Components1H8M3EpSchemasVirtualmachineidentityPropertiesUserassignedidentitiesAdditionalproperties
. Changing names of classes and methods breaks existing code. The nature of the new name suggests this change may be unintentional.To Reproduce
Steps to reproduce the behavior:
azure.mgmt.compute.models.VirtualMachineIdentityUserAssignedIdentitiesValue
:-)Expected behavior
This happened to us as a result of a routine upgrade to latest packages. We have been on
13.0.0
for a while, and latest is17.0.0
. We expected the routine upgrade to be seamless.The text was updated successfully, but these errors were encountered: