Closed rupprecht1993 closed 2 years ago
@lowmann15 Thanks for reporting this issue! Directing it to the right people.
similar issue : https://github.com/Azure/azure-sdk-for-python/issues/16984
@swathipil is there any chance to get a planned fixxing date? We are very dependent on that fix in an operational sense. Thanks!
@msyyc - Would you be able to reply to the above message with updates? Thanks!
The problem is caused by the difference between track1(version < 1.0.0b1) and track2(version >= 1.0.0b1). Track1 is deprecated and new content will be only published with track2. Please follow the guidance of https://github.com/Azure/azure-sdk-for-python/issues/16984 to complete migration.
some other useful guidance: https://devblogs.microsoft.com/azure-sdk/migrating-python-management-libraries/ https://github.com/Azure/azure-cli/blob/dev/doc/track_2_migration_guidance.md
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
Hi @lowmann15. 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 “/unresolve
” to remove the “issue-addressed” label and continue the conversation.
Hi @lowmann15, since you haven’t asked that we “/unresolve
” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve
” to reopen the issue.
Describe the bug Trying to upload an openapi.json file via the sdk to the api management results in a loss of schema information (in that particular case the "minLength" property).
To Reproduce requirements.txt:
main.py:
openapi.json:
Steps to reproduce the behavior:
Expected behavior All of the properties listed under "schema" are getting deployed.
Screenshots After execution in the API Management, not every schema property was deployed: