microsoftgraph / microsoftgraph/msgraph-sdk-python
`InvalidModel` when updating Access Package Assignment Policy
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 630
- 派生
- 96
- 平均合并
- 15 小时 20 分钟
- 30 天内合并 PR
- 3
描述
Describe the bug
I want to update an access package assignment policy, but whenever the policy includes the requirement for approval (i.e. is_approval_required_for_add=True), this fails with an InvalidModel error.
Example:
If I set the property for "requires approval" to false, I am able to retrieve an existing access package policy by ID and update a certain property (e.g. the duration) successfully:
# Retrieve the pre-existing access package assignment policy:
ap_assignment_policy_obj = await graph_client.identity_governance.entitlement_management.assignment_policies.by_access_package_assignment_policy_id(<ap_pol_id>).get()
# Set the required duration in ISO 8601 duration format:
ap_assignment_policy_obj.expiration.duration = "PT4H"
# Update the access package assignment policy:
result = await graph_client.identity_governance.entitlement_management.assignment_policies.by_access_package_assignment_policy_id(<ap_pol_id>).put(ap_assignment_policy_obj)
However as soon as "requires approval" is set to true (and the associated approval groups etc. are set), I am no longer able to update an existing access package assignment policy. Instead, the following error is encountered:
msgraph.generated.models.o_data_errors.o_data_error.ODataError:
APIError
Code: 400
message: None
error: MainError(additional_data={}, code='InvalidModel', details=[], inner_error=InnerError(additional_data={}, client_request_id='', date=datetime.datetime(2025, 6, 12, 12, 57, 48), odata_type=None, request_id=''), message='The model is invalid.', target=None)
Expected behavior
Regardless of whether or not approval is required (as dictated by the property is_approval_required_for_add), the access package policy update should work.
How to reproduce
- Create an access package assignment policy
- Set "requires approval" to true, and fill in the required properties
- Try to update the access package assignment policy
SDK Version
1.33.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
msgraph.generated.models.o_data_errors.o_data_error.ODataError:
APIError
Code: 400
message: None
error: MainError(additional_data={}, code='InvalidModel', details=[], inner_error=InnerError(additional_data={}, client_request_id='', date=datetime.datetime(2025, 6, 12, 12, 57, 48), odata_type=None, request_id=''), message='The model is invalid.', target=None)
Configuration
No response
Other information
An example of the approval settings that can be used to generate this error is shown below:
from msgraph.generated.models.access_package_assignment_approval_settings import AccessPackageAssignmentApprovalSettings
from msgraph.generated.models.access_package_approval_stage import AccessPackageApprovalStage
ap_assignment_policy_obj. request_approval_settings = AccessPackageAssignmentApprovalSettings(
is_approval_required_for_add = True,
is_approval_required_for_update = False,
is_requestor_justification_required = True,
stages = [
AccessPackageApprovalStage(
duration_before_automatic_denial = datetime.timedelta(days=14),
is_escalation_enabled = False,
is_approver_justification_required = True,
duration_before_escalation = datetime.timedelta(0),
primary_approvers = [
GroupMembers(
odata_type = "#microsoft.graph.groupMembers",
description = "approver_group"
)
],
fallback_primary_approvers = [],
escalation_approvers = [],
fallback_escalation_approvers = []
)
]
)
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 assignment_policies.by_access_package_assignment_policy_id().get() 和 .put() 开始,然后检查 AccessPackageAssignmentApprovalSettings 和 AccessPackageApprovalStage 的序列化。将 is_approval_required_for_add 设置为 true,并使用提供的审批阶段进行复现。更新现有策略时能够成功且不出现 InvalidModel 即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- api
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100