microsoftgraph / microsoftgraph/msgraph-sdk-python
`InvalidModel` when updating Access Package Assignment Policy
まだ誰も着手していません。
- 主要言語
- Python
- スター
- 630
- フォーク
- 96
- 平均マージ
- 15時間 20分
- マージ済み PR(30日)
- 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 にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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