Endpoint "/beta/deviceManagement/configurationPolicies" misbehaves when expanding property assignments for specific policy
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 25/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- powershell
- 領域
- api
研究方向
首先，針對 /beta/deviceManagement/configurationPolicies 重現兩個 Get-MgBetaDeviceManagementConfigurationPolicy 查詢，使用帶有和不帶 -DeviceManagementConfigurationPolicyId 的 -ExpandProperty assignments。比較 templateFamily 以 "endpointSecurity" 開頭的原則的指派資料；當目標查詢傳回與未篩選查詢相同的指派時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
This issue happens ONLY when the targeted policy is of a templateFamily that starts with "endpointSecurity".
I was trying to query the endpoint using the cmdlet:
Get-MgBetaDeviceManagementConfigurationPolicy -ExpandProperty assignments -DeviceManagementConfigurationPolicyId "PolicyID"
and, although the response had the property assignments in the body json, the assignments where empty.
Interestingly, if I query the endpoint without specifying a policy ID (Get-MgBetaDeviceManagementConfigurationPolicy -ExpandProperty assignments), it seems to actually return the data correctly for all the policies.
For the record, I replicated the same scenario in the graph explorer as well
Expected behavior
Expected behaviour would be to actually be able to expand the property assignments even when using the id to target a specific policy
How to reproduce
Execute the command Get-MgBetaDeviceManagementConfigurationPolicy -ExpandProperty assignments
Check that all the policies return the correct assignment data
Execute the command Get-MgBetaDeviceManagementConfigurationPolicy -ExpandProperty assignments -DeviceManagementConfigurationPolicyId "PolicyID"
Check that the returned data do not show any assignments.
Non Working query
Working query
SDK Version
2.28.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
Name Value
---- -----
PSVersion 7.5.1
PSEdition Core
GitCommitId 7.5.1
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
### Other information
Since this issue is tied to the endpoint not returning the correct data, I believe it is not tied to any of the SDKs. Should be a bug on the backend side,- 主要語言
- C#
- 星號
- 904
- 分支
- 235
- 平均合併
- 1 天 23 小時
- 30 天內合併 PR
- 22
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoftgraph/msgraph-sdk-powershell 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 84/100
microsoftgraph/msgraph-sdk-powershell#3752 ·
維護者通常 1 天內回覆
-
status:waiting-for-triage type:bug
難度 4/5 3-5 天 新手友好度 55/100
microsoftgraph/msgraph-sdk-powershell#3831 ·
維護者通常 1 天內回覆
-
status:waiting-for-triage type:feature
難度 5/5 一週以上 新手友好度 8/100
microsoftgraph/msgraph-sdk-powershell#3827 ·
維護者通常 1 天內回覆
-
status:waiting-for-triage type:bug
難度 4/5 3-5 天 新手友好度 22/100
microsoftgraph/msgraph-sdk-powershell#3822 ·
維護者通常 1 天內回覆
-
Connect-MgGraph on 2.41 crashes when making a connection with cert, fixes when using 2.39 or lower未關閉status:waiting-for-triage type:bug
難度 4/5 3-5 天 新手友好度 48/100
microsoftgraph/msgraph-sdk-powershell#3816 ·
維護者通常 1 天內回覆
查看 microsoftgraph/msgraph-sdk-powershell 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 77/100
維護者通常 1 天內回覆
-
enhancement no-stack-trace
難度 2/5 1-3 小時 新手友好度 66/100
greenshot/greenshot#1618 · 3 則留言 ·
維護者通常 1 天內回覆
-
squad/utforming status/triage
難度 2/5 1-3 小時 新手友好度 78/100
Altinn/altinn-studio#21565 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 67/100
Tyrrrz/YoutubeDownloader#912 ·
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆