You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This may or may not be a bug, but i noticed while creating custom profiles or passing specific api versions to the client, the operations versions change but not the models.
>>> conn.azure_sdk_client.operations
<azure.mgmt.compute.v2018_06_01.operations._operations.Operations object at 0x10416ea20>
but now check the models:
>>> conn.azure_sdk_client.models()
<module 'azure.mgmt.compute.v2019_07_01.models' from 'path in site-packages'
**Expected behavior**
I simply expected that the model versions would use the same as the operations, especially since they are all stored in the same version dir.
**Screenshots**
N/A
**Additional context**
To be fair I have not ran into any problems as of yet, though i find this concerning. if the latest default version (which is what the model seems to use) is applicable to all versions it seems misleading to store a copy in each version then pull from the latest. I would also be further concerned that if the models did differ the older operations would not align properly with the expected models.
The text was updated successfully, but these errors were encountered:
Describe the bug
This may or may not be a bug, but i noticed while creating custom profiles or passing specific api versions to the client, the operations versions change but not the models.
To Reproduce
Steps to reproduce the behavior:
ComputeManagementClient
along with other required fields.The text was updated successfully, but these errors were encountered: