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
client.device_management.configuration_settings.get() started returning Resource not found for the segment 'configurationSettings'. when my dependency cache expired and Kiota was upgraded from 1.9.0 to 1.9.1, because the SDK was requesting /configurationSettings instead of /deviceManagement/configurationSettings
Expected behavior
SDK calls don't randomly start failing when I've pinned the Graph SDK version
How to reproduce
I've reproed with SDK v1.19.0 too and Kiota 1.9.1
SDK Version
1.18.0
Latest version known to work for scenario above?
none, because the kiota dependencies aren't pinned. if I pin kiota 1.9.0 it works
Activity
pl4nty commentedon Feb 7, 2025
I'm seriously tempted to just
.with_urlall my Graph calls if the SDK dependencies remain unpinnedpl4nty commentedon Feb 7, 2025
Looks like it's unpinned in
msgraph-sdk-core. That's even worse, because graph v1.0 could be impacted toohttps://github.com/microsoftgraph/msgraph-sdk-python/blob/25d6c6c12f6b20a8c6b36f4fa9b7574c1826da0e/pyproject.toml#L13-L21
pl4nty commentedon Feb 7, 2025
dupe of microsoftgraph/msgraph-sdk-python#1089, hopefully this hasn't impacted our production services yet
Update to msgraph-beta-sdk==1.29.0 and explictly set msgraph beta URL…