Compatibility issues with latest autorest
See original GitHub issueBefore filling a bug
- have you checked the faq for known issues.
- have you checked existing issues
Describe the bug Previously version of autorest 3.1 started giving problems and i was forced to upgrade. The latest autorest 3.4 is using latest extensions of core and python which inherently is forcing us change versions of other packages likes moto, boto, boto3, botocore …etc.
Please provide as much information as you can. This would be:
- OpenAPI files having the issues
- Autorest command used
Expected behavior
After generating the autorest latest client, when making the request firstly it showed an error for the from azure.core.rest import HttpRequest rest not found – I was using azure-core 1.12, updating it to 1.18 resolved the problem. Then it started giving AttributeError: ‘_patch’ object has no attribute 'is_local Then updating mock version resolved this issue. However from mock, it depends/ has compatibility issues with moto, which indeed forced me to update versions of boto, boto3, botocore.
Additional context These are the current versions i’m using. Autorest versions [cli version: 3.4.0; node: v14.18.0] autorest/core – 3.6.3 info | Installing AutoRest extension ‘@autorest/python’ (latest) info | Installed AutoRest extension ‘@autorest/python’ (latest->5.9.1) info | Installing AutoRest extension ‘@autorest/modelerfour’ (~4.19.1) info | Installed AutoRest extension ‘@autorest/modelerfour’ (~4.19.1->4.19.3)
Previously was using 3.1 – is there any way, we can still continue using 3.1 and not upgrade or forced to update ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
Gooodd
Hi, we’re sending this friendly reminder because we haven’t heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don’t hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!