Operations related to /roleManagement/directory/roleAssignmentApprovals marked for deprecation in beta with no replacement
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- openapi
- Área
- api, authorization, documentation
Línea de trabajo
Comience con las definiciones de Beta OpenAPI.yaml en /roleManagement/directory/roleAssignmentApprovals y compare sus metadatos de obsolescencia con el registro de cambios de Microsoft Graph y la documentación de Entra ID approval-workflow. Determine si la obsolescencia es intencionada, identifique cualquier reemplazo para aprobar o rechazar asignaciones y documente las indicaciones confirmadas o la corrección de metadatos necesaria.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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}'
- Lenguaje dominante
- XSLT
- Estrellas
- 171
- Forks
- 56
- Merge medio
- 1 d 11 h
- PR fusionados (30 d)
- 9
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoftgraph/msgraph-metadata
-
ToTriage
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
microsoftgraph/msgraph-metadata#1217 ·
Los mantenedores suelen responder en 2 días
-
ToTriage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoftgraph/msgraph-metadata#1192 ·
Los mantenedores suelen responder en 2 días
-
ToTriage
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
microsoftgraph/msgraph-metadata#1233 ·
Los mantenedores suelen responder en 2 días
-
`microsoft.graph.managedDevice` is missing a filter restrictions annotation.Posiblemente ocupada @esidorenko-sl la tomó hace 86 días. AbiertoToTriage
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
microsoftgraph/msgraph-metadata#1193 · 2 comentarios ·
Los mantenedores suelen responder en 2 días
-
ToTriage
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
microsoftgraph/msgraph-metadata#1169 · 1 reacción ·
Los mantenedores suelen responder en 2 días
Todos los issues de microsoftgraph/msgraph-metadata
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
matomo-org/plugin-CustomAlerts#310 ·
Los mantenedores suelen responder en 1 día
-
A CSV row that removes a language with #CLEAR and fills another name of it keeps one of themAbiertobug level:trivial
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
exoego/keycloak-fuhito#666 ·
Los mantenedores suelen responder en 1 día
-
bug size:small
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
fb55/htmlparser2#2579 ·
Los mantenedores suelen responder en 1 día