azure-sdk-for-python icon indicating copy to clipboard operation
azure-sdk-for-python copied to clipboard

Not A Feature Request but Requesting Help with an Error When Calling Azure Python SDK

Open hacknorris opened this issue 3 years ago • 9 comments

We are getting some errors when trying to pull data and are requesting some assistance.

We are trying to call azure.mgmt.security.operations.ConnectorsOperation.list but are getting this error.

The first image is related to pulling connectors from Microsoft Defender for Cloud (Azure Security Center) and we would expect it to not error out.

sdk-connectors-error

The second image is related to settings operations when calling: azure.mgmt.security.operations.settings_operations.. It looks as the the api_version is hard coded to 2019-01-01. Is there a difference in endpoints between commercial cloud and government clouds?

sdk-gcc-error

Can you please help us?

hacknorris avatar May 24 '22 01:05 hacknorris

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Security:0.10406777,Azure.Core:0.0580057,azure-spring:0.04761129'

azure-sdk avatar May 24 '22 01:05 azure-sdk

Thanks for opening the issue @hacknorris! We will take a look and get back to you asap.

@BigCat20196 has already been assigned to dig deeper - but I will also tag the security team regarding your second question. It is definitely the case that some API versions can have varying support between the public and government clouds - and our SDKs should allow the API version to be overridden in these scenarios - so hopefully the Security team can clarify the supported API versions and then we can take a look at how this can be customized in the SDK.

annatisch avatar May 24 '22 19:05 annatisch

Thank you for your feedback. This has been routed to the support team for assistance.

ghost avatar May 24 '22 19:05 ghost

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @chlahav.

Issue Details

We are getting some errors when trying to pull data and are requesting some assistance.

We are trying to call azure.mgmt.security.operations.ConnectorsOperation.list but are getting this error.

The first image is related to pulling connectors from Microsoft Defender for Cloud (Azure Security Center) and we would expect it to not error out.

sdk-connectors-error

The second image is related to settings operations when calling: azure.mgmt.security.operations.settings_operations.. It looks as the the api_version is hard coded to 2019-01-01. Is there a difference in endpoints between commercial cloud and government clouds?

sdk-gcc-error

Can you please help us?

Author: hacknorris
Assignees: BigCat20196
Labels:

question, Security, Service Attention, Mgmt, customer-reported, needs-team-attention

Milestone: -

ghost avatar May 26 '22 03:05 ghost

Removing CXP attention label, This is being looked upon by the SDK and Service team.

@chlahav Could you please look into this ask when you get a chance ? Awaiting your reply.

navba-MSFT avatar May 26 '22 03:05 navba-MSFT

Hi @hacknorris, sorry for late reply.

For Q1, it may be caused by the low version of msrest. Please try to update it to the latest version.

For Q2, Different types of cloud support are different. It mainly depends on whether the version of API is deployed on the cloud. This is not controllable by the SDK. the supported API versions in the cloud have been given in the error message.

BigCat20196 avatar Jun 01 '22 03:06 BigCat20196

sorry @BigCat20196 - missed your reply on this. Can you clarify on the update of msrest for Q1. For Q2, does someone on the Microsoft product team have to update the API for GCC High?

hacknorris avatar Jun 10 '22 03:06 hacknorris

Hi, For Q1, please try to update msrest to 0.6.21. For Q2, you could open issue in https://github.com/Azure/azure-rest-api-specs/issues and then service team shall pick up it

msyyc avatar Aug 11 '22 08:08 msyyc

Hi @hacknorris. 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.

ghost avatar Aug 12 '22 16:08 ghost

Hi @hacknorris, 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.

ghost avatar Aug 19 '22 22:08 ghost