Closed cindraw closed 1 year ago
Thanks for reporting the bug. I didn't do a lot of testing with connection strings, since we try to move people towards configuring things in msticpyconfig and just connecting using a workspace name (ref to the config entry). I can fix this though.
Thank you for your response. I read the docs and found out that the connection string feature is being deprecated and have successfully used a config yaml file instead
Describe the bug The function
QueryProvider.connect()
fails to grab tenant or workspace IDs given a valid connection string.To Reproduce Steps to reproduce the behavior:
pip install msticpy[azsentinel]
QueryProvider
-from msticpy.data.data_providers import QueryProvider
LogAnalytics
environment -query_provider = QueryProvider(data_environment='LogAnalytics')
la_connection_str = f"loganalytics://tenant='{tenant}';workspace='{workspace}';alias='{alias}';clientid='{client_id}';client_secret='{client_secret}'"
query_provider.connect()
-query_provider.connect(connection_str=la_connection_str)
Expected behavior Tenant or workspace IDs should have been extracted successfully from a valid connection string
Screenshots and/or Traceback
Environment (please complete the following information):
Additional context It looks like the regex pattern matching for method
from_connection_string
inWorkspaceConfig
fails to extract IDs from a connection string. See the screenshots below for more information.