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 天内回复