Operations related to /roleManagement/directory/roleAssignmentApprovals marked for deprecation in beta with no replacement
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- openapi
研究方向
從 /roleManagement/directory/roleAssignmentApprovals 下的 Beta OpenAPI.yaml 定義開始,並將其棄用中繼資料與 Microsoft Graph 變更記錄和 Entra ID approval-workflow 文件進行比較。確認此次棄用是否為有意行為,找出是否有可用於核准或拒絕指派的替代項目,並記錄已確認的指引或所需的中繼資料修正。
由索引模型根據 Issue 內容生成。
描述
Hi,
We found that many of the operations that relates to roleManagement/directory/roleAssignmentApprovals/ are marked for deprecation, but we can't find any suitable replacement for approving or denying role assignments in Entra ID Privileged Identity Management.
More to that, we also can't find any related announcement in Microsoft Graph changelog.
The Entra ID documentation also doesn't state anything about the deprecation of those paths and still indicates to use them for our use case.
Am I reading the deprecation notice wrong in the SDK and in the OpenAPI.yaml for the beta API. Is there any planned replacement for the same operation?
Here is an exemple of operation that is marked for deprecation with a removal date of 2025-12-01'
Thank you or your input on this :)
/roleManagement/directory/roleAssignmentApprovals/{approval-id}/steps/{approvalStep-id}':
description: Provides operations to manage the steps property of the microsoft.graph.approval entity.
get:
tags:
- roleManagement.rbacApplication
summary: Get steps from roleManagement
description: Used to represent the decision associated with a single step in the approval process configured in approvalStage.
operationId: roleManagement.directory.roleAssignmentApprovals.GetSteps
parameters:
- name: $select
in: query
description: Select properties to be returned
style: form
explode: false
schema:
uniqueItems: true
type: array
items:
type: string
- name: $expand
in: query
description: Expand related entities
style: form
explode: false
schema:
uniqueItems: true
type: array
items:
type: string
responses:
2XX:
description: Retrieved navigation property
content:
application/json:
schema:
$ref: '#/components/schemas/microsoft.graph.approvalStep'
4XX:
$ref: '#/components/responses/error'
5XX:
$ref: '#/components/responses/error'
deprecated: true
x-ms-deprecation:
removalDate: '2025-12-01'
date: '2025-01-01'
version: 2025-01/PrivatePreview:microsoft.applicationAuthorization
description: This version is being deprecated and is scheduled for removal on 2025-12-01.Please migrate to the latest version before the removal date.
x-ms-docs-operation-type: operation
patch:
tags:
- roleManagement.rbacApplication
summary: Update the navigation property steps in roleManagement
operationId: roleManagement.directory.roleAssignmentApprovals.UpdateSteps
requestBody:
description: New navigation property values
content:
application/json:
schema:
$ref: '#/components/schemas/microsoft.graph.approvalStep'
required: true
responses:
2XX:
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/microsoft.graph.approvalStep'
4XX:
$ref: '#/components/responses/error'
5XX:
$ref: '#/components/responses/error'
deprecated: true
x-ms-deprecation:
removalDate: '2025-12-01'
date: '2025-01-01'
version: 2025-01/PrivatePreview:microsoft.applicationAuthorization
description: This version is being deprecated and is scheduled for removal on 2025-12-01.Please migrate to the latest version before the removal date.
x-ms-docs-operation-type: operation
delete:
tags:
- roleManagement.rbacApplication
summary: Delete navigation property steps for roleManagement
operationId: roleManagement.directory.roleAssignmentApprovals.DeleteSteps
parameters:
- name: If-Match
in: header
description: ETag
schema:
type: string
responses:
'204':
description: Success
4XX:
$ref: '#/components/responses/error'
5XX:
$ref: '#/components/responses/error'
deprecated: true
x-ms-deprecation:
removalDate: '2025-12-01'
date: '2025-01-01'
version: 2025-01/PrivatePreview:microsoft.applicationAuthorization
description: This version is being deprecated and is scheduled for removal on 2025-12-01.Please migrate to the latest version before the removal date.
x-ms-docs-operation-type: operation
parameters:
- name: approval-id
in: path
description: The unique identifier of approval
required: true
schema:
type: string
x-ms-docs-key-type: approval
- name: approvalStep-id
in: path
description: The unique identifier of approvalStep
required: true
schema:
type: string
x-ms-docs-key-type: approvalStep
x-ms-docs-grouped-path:
- '/roleManagement/enterpriseApps/{rbacApplication-id}/roleAssignmentApprovals/{approval-id}/steps/{approvalStep-id}'
- '/roleManagement/entitlementManagement/roleAssignmentApprovals/{approval-id}/steps/{approvalStep-id}'
- 主要語言
- XSLT
- 星號
- 171
- 分支
- 56
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 9
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
microsoftgraph/msgraph-metadata 的其他 Issue
-
ToTriage
難度 2/5 1-3 小時 新手友好度 86/100
microsoftgraph/msgraph-metadata#1217 ·
維護者通常 2 天內回覆
-
ToTriage
難度 2/5 1-3 小時 新手友好度 68/100
microsoftgraph/msgraph-metadata#1192 ·
維護者通常 2 天內回覆
-
ToTriage
難度 3/5 1-2 天 新手友好度 57/100
microsoftgraph/msgraph-metadata#1233 ·
維護者通常 2 天內回覆
-
`microsoft.graph.managedDevice` is missing a filter restrictions annotation.可能已有人在做 @esidorenko-sl 於 86 天前認領。 未關閉ToTriage
難度 3/5 1-2 天 新手友好度 72/100
microsoftgraph/msgraph-metadata#1193 · 2 則留言 ·
維護者通常 2 天內回覆
-
ToTriage
難度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/msgraph-metadata#1169 · 1 個 reaction ·
維護者通常 2 天內回覆
查看 microsoftgraph/msgraph-metadata 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
matomo-org/plugin-CustomAlerts#310 ·
維護者通常 1 天內回覆
-
bug level:trivial
難度 2/5 1-3 小時 新手友好度 72/100
exoego/keycloak-fuhito#666 ·
維護者通常 1 天內回覆
-
bug size:small
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
-
難度 2/5 1-3 小時 新手友好度 78/100
fb55/htmlparser2#2579 ·
維護者通常 1 天內回覆